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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful context beyond that: no account, payment, paid body, or private data is involved, and it supports clients unable to read MCP resources. Rate limits or auth specifics are not mentioned, but the annotations carry the safety profile.

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 description is compact and front-loaded, starting with what is returned and following with constraints, alternatives, and client compatibility. Every sentence adds selection or behavioral value, with no filler.

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?

Given that an output schema exists and annotations cover safety, the description provides everything else an agent needs: the free-workflow scope, the get_overview prerequisite, the premium alternative, and the client-resource limitation. No material invocation detail is missing for a simple one-parameter read tool.

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 does not explicitly define the required id parameter. However, it does link the id semantically to a workflow 'listed by get_overview,' which helps an agent understand where valid identifiers come from. The enum itself supplies the exact allowed values, so this is minimally adequate rather than rich.

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: 'Return the complete Markdown body of one free workflow.' It also distinguishes this tool from premium-product siblings by naming list_skills/get_skill as the alternative, so an agent can select it without opening another 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 usage conditions: the workflow must be listed by get_overview, and premium products should use list_skills/get_skill instead. It also adds the special case of clients that cannot read MCP resources, leaving no ambiguity about when this tool is appropriate.

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