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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds one genuinely new behavioral fact — 'Public access,' i.e. no authentication required — but says nothing about rate limits, response shape, or how codes are keyed. A 3 fits given annotation coverage carries most of the profile.

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 short, front-loaded sentences with no wasted words; the result contents are stated before the access note. 'Public access.' is terse to the point of being fragmentary, which slightly weakens structure.

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 zero-argument lookup with no output schema, the description tells the agent what information the call yields (fields, retryability, remedies), which is the key missing piece an output schema would otherwise supply. It is nearly complete; only the shape/format of the returned explanations is unspecified.

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?

The schema declares zero parameters, so there is nothing for the description to document. Baseline of 4 applies for a parameterless tool.

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 resource (documentary reason codes) and enumerates what the lookup returns: affected fields, retryability, and remedies. No sibling tool covers reason codes, so it is distinguishable by content even though it does not name an alternative. Slightly domain-specific vocabulary ('documentary') keeps it from a clean 5.

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 only guidance is 'Public access,' which describes an access/auth condition rather than when to reach for this tool. There is no statement of when to use it versus the many get_* siblings, nor any trigger condition such as 'use when a submission returns a reason code.'

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