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 covered. The description adds that the instructions are 'canonical' and intended for CLAUDE.md, but says nothing about the return payload or whether it is project-scoped versus generic — though an output schema exists, easing that gap.

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, zero filler, with the primary purpose front-loaded before the usage hint. Nothing could be removed without losing signal.

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 zero-required-parameter read tool with a fully documented enum and an output schema, the description covers what is needed to invoke it correctly. It could be slightly stronger by clarifying scope (project-specific vs. generic workflow docs), but the essentials are present.

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% and the single enum parameter (markdown vs section) is fully documented in the schema. The description adds nothing about the format parameter, so the baseline 3 applies: the schema does all the work here.

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 ('Get the canonical Damper workflow instructions'), which an agent can act on immediately. However, it does not differentiate from nearby sibling tools like get_project_context or sync_project_context, which could plausibly return overlapping project-setup content.

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 usage context: 'set up or update CLAUDE.md in a project.' That tells the agent when to reach for this tool. It stops short of naming exclusions or alternatives (e.g., get_project_context) for other project-context needs.

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