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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait — 'Bearer token required' — but says nothing about read-only behavior, rate limits, pagination, or what the returned status actually contains, leaving most behavioral questions unanswered.

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 with no filler, and the auth requirement is tucked at the end rather than buried. It is arguably too terse for a tool whose scope overlaps several siblings, but nothing is wasted.

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-parameter tool with no output schema and no annotations, the description establishes roughly what data is returned and the auth requirement, which is the minimum viable. It stops short of describing the return shape or how the 'plan/trial status' fields should be interpreted.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent arguments.

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?

The description names the resources it surfaces ('servers, plan and trial status') and implies a read of account data, but it has no verb and never says it retrieves/fetches anything. It also does nothing to distinguish it from siblings like annsurv_check, annsurv_limits or annsurv_pricing, which plausibly overlap with 'servers' and 'plan'.

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 when-to-use guidance whatsoever: no condition for choosing this over annsurv_check, annsurv_pricing, or annsurv_paths. The only context is the parenthetical auth note, which is a prerequisite, not usage guidance.

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