get_dev_task

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

Describes response contents (spec fields, dependency info, slug) and explains context_pointers short-circuits file discovery. No contradictions with annotations (none provided).

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?

Well-structured: main action, response details, parameter info. No fluff. Front-loaded with essential purpose.

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?

Output schema exists, so return description not needed. Covers purpose, parameter format, usage guidance, and response contents. Fully sufficient for a fetch-by-ID tool.

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 description coverage is 0%, but description explains task_id as 'ObjectId hex string (24 hex chars)' and directs to alternative tool for slugs, adding meaning beyond 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?

Explicitly states 'Fetch a single dev-task by its ObjectID.' Distinct from sibling 'get_dev_task_by_slug' which uses slug.

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?

Directly tells when to use this tool (when you have ObjectID) and when to use alternative (slug). Provides usage advice: read spec fields, use context_pointers.

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