get_webhook_stats

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful, non-obvious behavioral context: a Proof account is required, PROOF_API_KEY must be set with a restart, and notably start_login does not unlock this tool. It does not mention pagination or rate limits, but the access disclosure is valuable.

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?

Purpose is front-loaded in the first sentence, which earns its place. The access note is useful but slightly clunky ('Set PROOF_API_KEY and restart this server, then call this tool again'), adding a redundant call-again instruction that could be tightened.

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 partially compensates by listing the metrics returned. Combined with the explicit account/API-key prerequisite, an agent has enough to invoke it correctly, though return format specifics (e.g., shape of 'recent activity') remain unspecified.

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 the baseline of 4 applies. There is nothing for the description to disambiguate beyond the fact that no filtering arguments exist.

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 ('Get') and resource ('webhook delivery statistics') and enumerates the returned content (total deliveries, success/failure counts, recent activity). This clearly separates it from siblings like list_webhook_deliveries and get_webhook_delivery, which deal with individual deliveries rather than aggregates.

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?

Usage is implied (use for aggregate stats rather than per-delivery inspection), but the description never explicitly contrasts this with list_webhook_deliveries or get_webhook_delivery. The second sentence is an auth prerequisite, not a when-to-use rule, so guidance stays at the inferred level.

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