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

Annotations declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, so the agent learns this is non-destructive but not read-only, yet the description says nothing about side effects, whether the check is recorded, permissions, or rate limits. A "Check" verb sitting on top of readOnlyHint=false is a tension the description should resolve but does not.

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?

A single short sentence that is front-loaded and free of filler, which is good, but it is thin enough to read as under-specification rather than disciplined brevity for a tool in a crowded namespace.

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?

With no output schema, an opaque pass-through body parameter, and dozens of adjacent *_check/*_catalogue siblings, the definition should carry the burden of explaining the request contract and result shape. It does not, leaving an agent unable to call this confidently versus alternatives.

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 nominally 100% (one body parameter), so the baseline is 3. However, the schema entry only says "See the AffixIO OpenAPI schema resource for the contract," so the description adds no real semantics about what the body must contain for this specific check.

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?

"Check clearance eligibility and guidance fit" gives a verb (check) and a resource (clearance), but "guidance fit" is undefined jargon and the phrasing does not separate this tool from siblings such as clearance_catalogue, drive_pass_check, or right_pass_check. An agent knows the general domain but not the specific operation.

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?

There is no statement of when to use this versus the many other *_check tools, no prerequisites (e.g. an identifier or pass token required before calling), and no exclusions. The agent is left to infer routing entirely from the name.

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