ats_pipeline_analytics

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

The description details the return values (stage distribution, conversion rates, etc.), adding behavioral context beyond the readOnlyHint annotation. It does not mention side effects or permissions, but as a read-only analytics tool, this is sufficient.

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 two sentences, front-loaded with the main action, and no wasted words. Every sentence adds value.

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, the description fully explains what the tool returns and its use case. The annotations and schema are well-covered, making the description complete for an agent to understand and invoke the 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?

The input schema has 100% description coverage for all three parameters, so the description adds minimal additional meaning. It mentions 'given candidates and optional pipeline stage config' but does not elaborate 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 clearly states the tool's purpose: 'Analyze the ATS hiring pipeline' and specifies the outputs (stage distribution, conversion rates, time-in-stage, bottlenecks). It distinguishes from sibling tools by focusing on pipeline analytics, not general candidate management or dashboard stats.

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 description says 'Useful for hiring funnel analysis,' which implies the context of use. However, it does not explicitly exclude alternatives or provide when-not-to-use guidance, but the purpose is clear enough for an agent to infer suitability.

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