get-todo-task

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

Annotations already indicate read-only and non-destructive. Description adds crucial behavioral details: $select fails with a specific error, use $expand to include linked resources, returns HTML body content, checklist items, and linked resources. This significantly enriches the agent's understanding beyond annotations.

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?

Front-loaded with purpose statement. Includes a helpful tip section. Minor redundancy: 'Returns a single To Do task' repeats the purpose. Could be slightly more concise, but overall well-structured.

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?

Despite no output schema, description specifies return content (HTML, checklist items, linked resources). Warns about an error-prone parameter ($select). Covers key aspects for a read operation. Annotations (readOnlyHint, openWorldHint, destructiveHint) complement well.

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% with parameter descriptions. Description adds critical meaning for the 'select' and 'expand' parameters (warning on $select, recommendation for $expand), which is not evident from schema alone. Other parameters are adequately described in 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?

Clearly states the action 'Read' and the resource 'todoTask object'. Differentiates from sibling 'list-todo-tasks' which lists multiple tasks, as it returns a single task.

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 explicit guidance on what not to use ($select causes error) and what to use instead ($expand for linked resources). Implies it is for retrieving a single task, but does not explicitly contrast with siblings like 'list-todo-tasks' or 'list-todo-linked-resources'.

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