ats_manage_offers

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

Annotations indicate destructiveHint=true, and the description reinforces this with actions like delete and update_status. It also discloses a status flow (draft→pending-approval→...) and states returns structured offer data, adding value beyond annotations.

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 front-loaded with the core purpose and lists actions efficiently in two sentences. Every sentence adds value, with no redundant or unnecessary words.

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 the tool's complexity (6 actions, nested parameters) and the presence of detailed schema, the description covers each action's purpose and basic flow. It lacks explicit details on return structure or error handling, but the schema compensates.

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 100%, so the schema already documents all parameters fully. The description adds high-level context (e.g., 'validate (check for issues)') but does not provide additional parameter meaning beyond what the schema offers.

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 begins with 'Manage offers in the ATS' and enumerates specific actions (create, update_status, delete, list, compare, validate) each with a brief verb+resource description. It clearly distinguishes from sibling tools (e.g., ats_manage_candidates, ats_manage_jobs).

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 implies the tool is for managing offers but does not explicitly state when to use it versus alternatives. No exclusions or conditions are mentioned; guidance is implicit through the resource name and sibling context.

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