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

With no annotations provided, the description carries the full burden and does disclose the key non-obvious behaviors: a Proof account is required, the hitl_channels sub-object requires the hitl:read scope, and start_login does NOT open this tool. It stops short of explicitly stating the call is read-only with no side effects, though 'snapshot' and 'dashboard renders' strongly imply it.

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?

The core purpose is front-loaded in the first sentence, followed by a compact bullet-like contents list. The ACCESS block is the only longer section, but every clause earns its place: account requirement, exact auth path, and the corrective note that start_login does not grant access. No filler.

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 carries the return-value burden and handles it well by enumerating all major snapshot components; the schema fully documents the environment scoping parameter. The remaining gap is that the failure mode when unauthenticated is only implied ('then call this tool again') rather than stated, but this is a minor omission for a parameter-light read tool.

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 100%: the single environment parameter is fully documented with enum values, default, and scoping semantics. The description adds no parameter-level information beyond the schema, so the baseline 3 applies.

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 pair ('Get... account snapshot') and enumerates the exact contents: quota with end-of-month projection, request health counts plus success rate, per-channel completion rates, HITL counts, and active API key count. Anchoring it to 'the same data the dashboard home renders' makes the resource concrete and distinguishes it from sibling getters like get_usage or list_api_keys that fetch individual slices.

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 'one-call account snapshot' framing implies when to use it (a broad overview rather than a single metric), and the ACCESS block gives actionable auth preconditions ('Authenticate this client... then call this tool again'). However, it never names alternative tools such as get_usage, list_hitls, or list_api_keys, nor states when to prefer those, leaving sibling selection to inference.

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