Delete a Boardroom todo

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

Clearly states hard-delete behavior and that comments are also deleted. The 'agent_id' requirement for audit is disclosed. Could mention irreversibility more explicitly, but 'hard-deletes' implies it.

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 with no filler. First sentence states core action, second provides usage guidance and parameter hint. Highly efficient.

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?

Covers key operational details for a simple delete operation. Lacks mention of idempotency or error handling (e.g., what happens if todo not found), but overall sufficient for agent understanding.

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?

Description adds meaning for 'agent_id' (required for audit log) beyond the schema, but 'todo_id' gets no extra context. With 0% schema coverage, the description partially compensates but not fully for both parameters.

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?

Name 'delete_todo' and title 'Delete a Boardroom todo' directly state the action and resource. Description clarifies it's a hard-delete that also removes comments, and distinguishes from the sibling 'drop_todo' which preserves history.

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?

Explicitly advises using 'drop_todo' instead for history preservation, and notes that 'agent_id' is required for audit logging. This gives clear when-to and when-not-to guidance.

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