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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, yet the description says simply 'Check', which reads as a passive read. That gap (a non-read-only, non-idempotent check that may record or consume something) is exactly what the description should explain, and it does not. No mention of quota, auth, or side effects.

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 front-loaded sentence with no padding — the purpose is stated immediately. Brevity is not itself a flaw, though the sentence is arguably under-built rather than efficient given everything left unsaid.

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 tool whose only input is an undocumented request body, with no output schema and non-read-only annotations, the description leaves the agent unable to know what to submit or what happens on call. It is a name-restatement rather than a usable contract.

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%, so the baseline is 3; however the single 'body' parameter's description only defers to an external OpenAPI resource ('See the AffixIO OpenAPI schema resource for the contract'), so the actual request contract is opaque in both places. The tool description adds nothing about body shape or required fields.

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?

States a specific verb + resource: 'Check permission or right-to-access eligibility with Right Pass.' An agent can tell it is an eligibility-check tool rather than a catalogue or issuance tool. It does not, however, distinguish itself from the close sibling set (right_pass_catalogue, drive_pass_check, clearance_check) or say what entity is being checked.

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?

No statement of when to call this versus right_pass_catalogue (likely the list-what-exists sibling) or drive_pass_check (an adjacent pass-check sibling). No prerequisites, no input requirements, no exclusions. The agent must infer usage 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.