Create a Boardroom todo

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

Without annotations, the description partially fills the transparency gap by noting that a 'todo-created' Boardroom event is posted. However, it does not disclose potential side effects like overwriting, rate limits, or permission requirements, nor does it describe the return value or confirmation behavior.

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?

The description is concise with three sentences, each serving a distinct purpose: what the tool does, when to use it, and what parameters are needed plus side effect. No filler or redundant information.

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 simple create tool, the description covers creation, usage scenario, parameters, and the event side effect. It does not explain prerequisites (e.g., existence of a board) or return value, but given the lack of output schema and the tool's straightforward nature, it is reasonably complete.

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 high (80%), so the description adds limited value. It explains that agent_id is the caller's ID and that title is short, but it does not elaborate on the enum values for priority or clarify the 'assignee' parameter 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 the tool creates a new todo card on the Boardroom Todos kanban, making it visible to both the agent and human. It specifies the content (action items needing tracking) and distinguishes from other todo tools by focusing on creation with event notification.

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?

The description provides explicit guidance on when to use the tool: 'Use when you decide an action item needs tracking beyond a single message: a follow-up task, a chore, a deliverable.' It does not explicitly mention when not to use or name alternatives, but the context is sufficient for basic decision-making.

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