get_todo

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

With no annotations provided, the description carries the behavioral burden. It adds useful context about authenticated-user scoping and single-item retrieval, but it does not disclose what happens when the todo is not found, whether the operation is read-only in explicit terms, or what the response contains.

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 a single, focused sentence with no filler. The key information—action, resource, ownership scope, and lookup key—is front-loaded and immediately usable.

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 single-parameter read operation, the description covers the core calling intent. However, with no output schema and no annotations, return value details and error behavior are left unexplained, which leaves gaps for an agent relying solely on this definition.

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 schema only defines todo_id with a title and minLength, and schema description coverage is 0%. The description adds minimal meaning by indicating that the ID is used to select the todo, but it does not explain where the ID comes from, its expected format, or any constraints 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 uses a specific verb ('Get') and resource ('one of the authenticated user's todos'), with a clear selection mechanism ('by ID'). It is immediately distinguishable from sibling list_todos because it explicitly refers to a single todo rather than a collection.

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 intended use is implied: call this when you have a todo_id and need that specific todo. However, it does not explicitly state when to prefer list_todos for multiple todos or mention any exclusions, so the guidance is only inferred rather than stated.

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