Create a Boardroom todo

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

No annotations provided, so description carries full burden. It mentions posting a 'todo-created' Boardroom event, which is a useful behavioral side effect. However, it omits details on failure cases, authorization, or rate limits.

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 core action, no redundant information. Each sentence adds value: purpose, usage guidance, and behavioral note.

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 creation tool with 5 parameters (2 required) and no output schema, the description covers purpose, usage scenario, and a key side effect (event posting). It could mention return value, but not required without schema. Adequate overall.

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 80% (4 out of 5 parameters have descriptions). The description restates parameter names ('agent_id, title, optional description, priority, assignee') without adding new meaning beyond the schema.

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?

The description clearly states 'Creates a new todo card on the Boardroom Todos kanban', specifying the verb and resource. It distinguishes from sibling tools like complete_todo and delete_todo by mentioning the kanban and cross-visibility for agent and human.

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 states when to use: 'Use when you decide an action item needs tracking beyond a single message'. While it doesn't list exclusions or alternatives, the context is clear given sibling tool names.

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