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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuine context beyond that: the endpoint path, that the call is free (cost/billing relevance), and that results break down by status and reason. It does not mention auth scoping or response size/limits.

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 sentence that front-loads the resource, then the breakdown content, then the endpoint and cost note. No filler, nothing redundant.

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 two-parameter, all-optional read tool with full schema coverage and no output schema, the agent knows what it gets back at a high level (status and reason breakdowns). It doesn't clarify the response shape, auth scoping, or how 'total only' interacts with the breakdowns when lifetime is used, leaving moderate gaps.

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%, with the period enum fully documented including the lifetime 'total only — no breakdown' caveat and the connection_id/lifetime incompatibility. The description adds nothing parameter-specific beyond 'calendar period', so 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 resource (verification usage report) with its content (status and reason breakdowns) and even the underlying endpoint, so an agent can tell it apart from siblings like get_account or get_batch_results. It stops short of explicitly naming which sibling to use instead for other reporting needs.

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 or when-not-to-use guidance and no named alternative among the 15 siblings. The only directional cue is the cost note 'Free', which hints at a cost preference but doesn't tell the agent when this report is the right call versus get_account or list_jobs.

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