codebase_start_job_analysis

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

Discloses async behavior and return content (analysis, recommendations, etc.), but lacks detail on error handling, permissions, or side effects. With no annotations, more behavioral context is expected.

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 with bold emphasis, front-loading purpose. Some repetition of instructions between description and parameter schema, but overall efficient.

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?

Given 2 parameters, output schema, and siblings, description covers async nature, single-entity focus, sibling precedence, and usage pattern. Missing error/cancellation notes but still solid.

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 100% of parameters; description adds value by reinforcing the query's required focus and one-topic rule. Adds meaningful guidance beyond schema basics.

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?

States 'Start async codebase analysis' with specific verbs and resource, and distinguishes from siblings by emphasizing single-entity analysis and preference for related_files_search. Clear and differentiated.

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?

Explicitly suggests using codebase_start_job_related_files_search first, and mandates one topic per request with wait-for-result pattern. Provides clear when-to-use and when-not-to.

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