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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new piece of context — that only approved metadata fields are exposed, with no secrets, contacts or files — but says nothing about auth requirements, pagination behavior, or result size.

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 sentences with the operation front-loaded and no filler beyond the slightly empty "through the existing application" clause. Efficient, though the brevity here reflects under-specification rather than tight writing.

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?

A read tool with three undocumented parameters, no output schema, and no explanation of what a 'billing status' payload contains. With no output schema to carry return semantics, the description should describe the shape of the response, and it does not.

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% across three parameters, and the description mentions none of them. The 'query' parameter in particular is completely opaque — query billing status by what? limit/offset suggest pagination that the description never acknowledges, leaving the agent to infer it from defaults alone.

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?

"Read authorised billing status" gives a verb and a resource, but "billing status" is left undefined — it could mean subscription plan, invoice/payment state, or seat counts, and an agent cannot tell which. There is no differentiation from the nearest siblings such as get_business_plans or get_tenant_capability_map, and "through the existing application" adds no discriminating information.

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 description never says when to call this versus alternatives, nor any prerequisites. The only scoping sentence ("Metadata/approved fields only; no secrets, contacts or original files") restricts what data is returned, not when the tool should be selected over a sibling status/plan tool.

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