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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description aligns with these by saying 'Read'. It adds context about requiring admin_token for authorization and describes what data is returned, which goes beyond the annotations.

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 sentences: the first front-loads the action and output, the second states the prerequisite. No unnecessary wording or repetition.

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?

The description is complete for a read-only tool: purpose, output data, prerequisite, and user intent (coaching) are all covered. The output schema and annotations handle return values and safety, so nothing critical is missing.

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 33%; admin_token and calendar_id lack descriptions. The description compensates by stating they come from create_calendar, providing important origin context. The 'today' parameter is already documented in the schema, so it doesn't need repetition.

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?

Clearly states the tool reads structured progress for a sprint calendar with specific metrics (execution %, streaks, missed sessions, metric vs guide, at-risk flags). The verb 'Read' and the specific resource distinguish it from sibling tools like read_document or list_templates.

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?

Provides a clear prerequisite: calendar_id and admin_token must come from create_calendar, indicating when to use this tool after calendar creation. However, it does not explicitly name alternatives or state when not to use it, but the guidance is sufficient for the intended use case.

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