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

No annotations provided; description discloses that cancellation is visible in hub and iCal, but does not mention reversibility, permissions, or other side effects. Adequate but lacks depth.

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, front-loaded with purpose; no unnecessary words.

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 a mutation tool with no output schema and no parameter descriptions, the description is missing important details like required permissions, response format, and parameter syntax. However, for a simple cancellation it is somewhat adequate.

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 has 0% description coverage; the description does not mention any parameter names or provide context for event_id or reason. No added meaning.

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?

Clear verb 'Mark as canceled' on 'program event'; distinguishes from sibling tools like org_add_program_event. Also states effect on enrolled parents.

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?

Description provides context that cancellation is visible to parents, but does not explicitly state when to use vs other tools (e.g., no mention of alternatives or when not to use).

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