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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: that workflows are created only in the dashboard and this tool merely lists them, plus the side effects (created as in_approval, approvers notified, publishes at schedule_at after final approval) of using a returned id.

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?

Three sentences, front-loaded with what is listed, then the create-vs-list boundary, then the operational guidance and empty-state instruction. No filler; every sentence changes agent behavior.

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?

Despite no output schema, the description specifies the returned content (steps, named approvers) and the empty-list handling. For a zero-parameter read tool with annotations already covering the safety profile, nothing an agent needs is missing.

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?

The tool takes zero parameters, so the baseline is 4. The only identifier mentioned (approval_workflow_id) belongs to create_post, not this tool, and the description correctly frames it as a value this tool produces to be consumed elsewhere.

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?

States a specific verb and resource with explicit scope: company-wide plus workspace-bound workflows, including that steps and named approvers are returned. No sibling tool overlaps this resource, so differentiation is inherent.

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?

Tells the agent exactly when to call it ('Call this first when the user wants agent-created posts to be reviewed/approved before publishing') and what to do on the empty case ('tell the user to create a workflow under Approvals in the dashboard'). It also names the downstream alternative path via create_post's approval_workflow_id.

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