get_task

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

Explicitly calls this a 'reads' operation, implying read-only behavior. Discloses returned fields (frontmatter, description, subtasks, notes). With no annotations, the description adequately conveys the tool's side-effect-free nature.

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 efficient sentences with no wasted words. Front-loaded with main action and required input, then lists what is returned.

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 get-by-id tool with one parameter and no output schema, the description adequately explains what is returned. Could optionally mention that the output includes the full task object, but the listed fields suffice.

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 covers the single parameter with an example. Description reinforces 'by ID' but adds no new semantic details beyond what the schema provides. Schema coverage is 100%, so baseline 3 is appropriate.

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 action (reads/returns) and resource (specific task by ID). Distinguishes from siblings like list_tasks or search_tasks by specifying retrieval of a single task's full metadata.

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?

Implies use when you have a task ID and need all metadata, but lacks explicit guidance on when to prefer this over siblings like get_next_task or search_tasks. No exclusions or conditions provided.

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