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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds the real added value here - the authentication requirement and the fact that the payload is a prescriptive playbook rather than a summary. No contradiction with annotations, and auth context is exactly the kind of extra disclosure that matters.

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?

Front-loads the auth prerequisite, then the payload description, then the behavioural instruction, in two tight sentences with no filler. Slightly dense but every clause carries information.

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?

Covers auth and expected return content well enough for a read-only tool with no output schema. However, with four parameters, 25% schema coverage and three overlapping identifier fields, the description leaves a real ambiguity (which id to pass) unresolved for an agent trying to invoke it.

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 coverage is only 25% and three near-synonymous identifier parameters (id, name, workflow_id) are left undocumented in both places; the description says 'one workflow id' but never disambiguates which parameter to use. The session parameter it alludes to is already fully described in the schema, so the description compensates very little 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 concrete verb+resource: it returns the complete step-by-step playbook for one workflow id, and enumerates the content it carries (decision gates, EU procurement eligibility rules, pitfalls). It does not name list_workflows to contrast itself, but 'one workflow id' implicitly separates it from the listing sibling.

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?

Gives a clear precondition chain (call connect_start(email) and connect_verify unless already signed in via OAuth/key) and an operating instruction ('follow it rather than summarising it'). It never states when to prefer this over list_workflows or get_opportunity, so it stops short of explicit alternatives.

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