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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only the scope fact that unpublished drafts are included; it says nothing about pagination behavior, result ordering, or caps on returned items, which an agent with required limit/offset would want.

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?

Two short sentences with no filler, and the differentiating scope statement is front-loaded before the sibling pointer. Nothing extraneous, though it is arguably too terse for a four-parameter listing tool.

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?

With 4 undocumented parameters, no output schema, and no explanation of pagination or result shape, the description leaves too much for the agent to guess. Required limit/offset in particular demand at least a note on paging behavior.

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 0%, and the description supplies no information about q, limit, offset, or project_id. The four parameters — including the meaning of the free-text search and the project scoping filter — are entirely undocumented, so the description fails to compensate for the coverage gap.

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 ('Find accessible workflows including unpublished drafts'), and the draft inclusion is a meaningful distinguishing scope note versus list_workflows. It stops short of explicitly contrasting with list_workflows, so sibling differentiation is only implied.

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?

The sentence 'Use get_workflow_draft to inspect before editing' does route the agent to a sibling for a related task, which is useful. However, it never says when to choose this tool over list_workflows, nor any prerequisites for accessing drafts (permissions, ownership).

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