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

Annotations already establish that this is a safe, read-only, idempotent, closed-world lookup. The description adds useful behavioral detail that an empty slug lists known ATSs and that content covers automation blockers/workarounds, but it does not describe unknown-slug behavior, result freshness, or other operational traits.

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 short and front-loads the core purpose before the empty-slug behavior. The parenthetical ATS list is useful but slightly crowded, keeping it just below maximally concise.

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?

For a simple one-parameter read-only lookup with an output schema, the description gives enough context to call the tool correctly. The main missing piece is how invalid or unknown slugs are handled, but that is minor given the annotations and output schema.

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%, so the description must carry parameter meaning. It does so by identifying the slug as an ATS identifier, giving example ATS values, and explaining that an empty slug returns the list of known ATSs; only format/case/unknown-value behavior remains unspecified.

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 that this tool returns quirks and workarounds for hiring systems/ATSs, including what blocks automation. It distinguishes itself topically from sibling tools like search, company, and check_posting, though it does not explicitly name those alternatives.

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?

Usage is implied: the tool is for understanding ATS-specific automation blockers and workarounds, and an empty slug lists known ATSs. However, it gives no explicit when-to-use vs alternative guidance, nor any exclusions for cases better served by sibling tools.

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