Afficher le tableau des ToDos

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

Without annotations, the description indicates it displays an interactive table but doesn't explicitly state read-only behavior or other traits. However, the purpose implies non-destructive use, and the output format is described.

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 concise sentences, front-loaded with purpose, followed by usage guidelines and alternative. No wasted words, easy to parse.

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?

The description covers purpose, usage, output fields, and alternative tool. It is adequate for a simple display tool, though it could mention any prerequisites like viewer context.

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 100%, so baseline is 3. The description adds context by mentioning 'latest project ToDos' and listing displayed fields, providing meaning beyond schema descriptions.

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 shows an interactive table of latest ToDos with specific fields. It explicitly distinguishes itself from the sibling tool tc_todos, which provides plain data without UI.

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 explicitly says when to use this tool (user asks to SEE/DISPLAY) and when not to (use tc_todos for plain data). It also provides example queries, giving clear guidance.

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