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

Annotations already declare readOnly/indempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the step list is paginated and bounded (50 default, 200 max), so the agent knows results may be partial and may need the limit raised — though the returned field list largely duplicates the output schema.

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 the trigger condition, then return contents, then the exclusion. No filler or redundancy; 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?

For a read-only trace tool with a full input schema, an output schema, and complete annotations, the description supplies everything else an agent needs: purpose, trigger, exclusion, and the bounded nature of the step page.

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 100%, so runId, projectId and stepLimit are already documented in the schema; the description's restatement of the 50/200 step bounds adds no syntax or semantics beyond that. Baseline 3 applies.

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?

Names a specific verb and resource (read one CronCool workflow execution plus a bounded page of its step statuses) and gives the intent (troubleshooting). The closing 'Not for listing runs' separates it from list_workflow_runs without the agent needing to open either 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?

Opens with an explicit trigger condition ('Use this when the user wants to read one ... for troubleshooting') and closes with an explicit exclusion ('Not for listing runs'), pointing the agent at the listing sibling by implication. Both when-to-use and when-not are stated.

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