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

Annotations already declare readOnlyHint=true, but the description adds an auth requirement ('Requires billing.read') and the retrieval semantics ('latest ... per kind', statuses pending/approved/rejected), which are not in the annotations. It does not discuss volume, pagination, or visibility scoping, so it stops short of a 5.

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 tight sentences: the first defines the resource, scope, and returned fields; the second carries the permission requirement and the read/write routing. No filler, and the most decision-relevant routing cue is last in a short payload.

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, the description compensates by stating the returned fields and status values, and it covers the authorization prerequisite. For a zero-parameter read tool this is sufficient for an agent to call it correctly.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool is 4. The description correctly implies the listing is organisation-wide and unfiltered, which is consistent with an empty schema.

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 (list/latest) plus resource (organisation limit-increase requests), scopes it to 'per kind', and enumerates what each entry contains: requested amount, justification, and status. It is trivially distinguishable from sibling request_limit_increase.

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?

Names the sibling alternative explicitly ('request_limit_increase files a new one'), which tells the agent exactly when to use this read tool versus the write tool. It also names the CLI counterpart 'ankra org limits list', anchoring expected behavior.

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