List Boardroom todos

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

Describes a read operation ('Returns todos'), but lacks details on pagination, sorting, or output format. No annotations to supplement, so it is minimally adequate.

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 concise sentences, front-loaded with purpose, no unnecessary words. Efficient and clear.

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 core purpose and primary use case, but lacks details on pagination, sorting, or output behavior. Sufficient for a simple list tool but not comprehensive.

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?

The description adds meaning for the status parameter ('optionally filtered by status') and reinforces agent_id as required, but does not explain assigned_to_agent_id or limit beyond the schema's 50% coverage.

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 it returns todos for the tenant, optionally filtered by status. It distinguishes from 'list_actionable_todos' by scoping to the tenant, but does not explicitly differentiate.

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 use cases ('render a kanban view, find your assignments, or pick the next thing to work on') and mentions status filtering, but does not specify when not to use or mention alternative tools.

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