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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own — no semantics for the 'match' operation, no indication of required scoping, no note on result shape or side effects.

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?

The first sentence is duplicated verbatim, so there is literal waste, and there is no front-loaded statement of intent. The remaining content is a bare operation ID plus a pointer to a sibling.

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?

For a nested-object, zero-coverage, no-output-schema tool, the description does not supply enough to construct a valid call. Pointing to describe_operation is the only mitigation, and it is a workaround rather than completeness.

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 two parameters (a free-form nested 'query' object and an empty 'params' object) have no documentation. The description offers no substitute — it only deflects to describe_operation, leaving the agent unable to know what query keys the match endpoint expects.

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 only restates the endpoint path and title ("GET /api/approvals/workflows/match") twice. It never explains what a 'workflow match' is or what resource is returned, so an agent cannot distinguish it from get_approvals_workflows_2a0387653a690414289f8f19 or get_approvals_workflows_by_id_b9119347bbee34968bcd76af.

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?

There is no when-to-use, when-not-to-use, or sibling comparison. The only navigational help is the pointer that describe_operation exposes native request schemas, which tells the agent how to get a schema, not when this tool is the right choice.

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