ats_search

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

Annotations already indicate read-only behavior. Description adds the key constraint that the full ATS state must be passed, which is critical for the agent to understand the input requirement.

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 sentences plus an enumeration convey the tool's purpose and actions without redundancy. The purpose is front-loaded, and 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?

Covers all three actions with their parameters adequately. However, no output schema or return description is provided, which would be helpful for a tool with multiple action outcomes.

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%, but description adds meaning by detailing the three possible action objects and their fields (e.g., filter_candidates includes stage, jobId, tags, minScore), complementing the schema's high-level description.

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 'Global search across the ATS' and enumerates three distinct actions (search, filter_candidates, get_entity), distinguishing it from sibling tools that manage specific entities.

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 usage through 'Global search' phrasing and action descriptions, but lacks explicit when-to-use or when-not-to-use guidance relative to sibling tools like ats_manage_candidates.

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