Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false, but the description frames this purely as a listing whose approval step 'happens only in the inbox, never through this call' — i.e., it claims a non-mutating read while the annotation says the call is not read-only. An agent relying on the safety hint gets a conflicting signal; this is an annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the approval-only constraint are front-loaded in the opening two sentences, and most sentences earn their place. The closing 'platform-prepares-never-sends handoff' sentence adds caller context but is jargon-heavy and slightly repetitive of the earlier 'never through this call' point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The conceptual model is complete — what is listed, what is excluded, ordering, and limit behavior — which is important since there is no output schema. However, with nine parameters and near-zero schema coverage, the description says nothing about how name, trigger_type, is_active, or definition_json affect the result, leaving an agent unable to invoke it precisely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 11% (only limit is documented), so the description must compensate and does not. It restates limit (1-100, default 50) and adds ordering ('newest-decided first'), but leaves eight parameters — name, is_active, role_name, description, next_run_at, trigger_type, imported_from, definition_json — unexplained, several of which look unrelated to listing prepared outputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — listing a tenant's APPROVED prepared outputs — and defines that resource as drafts from a workflow's prepare_output nodes that a human approved in the platform inbox. An agent can tell exactly what this returns and how it differs from pending/rejected drafts without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-not guidance: pending and rejected drafts never appear, and approval happens only in the inbox, never through this call. It also frames the caller ('the desktop harness pulls approved drafts here and sends them locally'). It stops short of naming an alternative tool (e.g., workflow_list) for a different question, so it is strong but not fully explicit about alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.