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

Beyond the annotations (which only declare non-read-only, non-destructive, closed-world), the description discloses a concrete rate limit (at most 10 per hour), idempotency semantics via client_ref (same key returns the first result and sends nothing new), and consent/privacy constraints on message content. These are real behavioral traits an agent cannot get from structured fields.

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?

Front-loaded with purpose, then usage triggers, then parameter guidance in a compact telegraphic style; every clause carries instruction. The dense parameter run-on reads as a spec dump, 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?

There is no output schema, and the description still covers the relevant return behavior in idempotency terms (same client_ref returns the first result), plus limits, privacy rules, and consent workflow. Nothing an agent needs to invoke this six-parameter write tool correctly is missing.

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 coverage is already 83%, so the baseline is 3; the description reinforces the key parameters with operational framing (type enum values, the 4000-char message bound, client_ref as a safe-retry key, contact_email only for replies, prompted_by only when a Povver note asked). Much of this restates schema descriptions, but the retry-safety and consent framing adds usable meaning.

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 (send) and resource (bug report, feature request, feedback) addressed to a named recipient (the Povver team). No sibling tool overlaps with this capability, so an agent can select it without ambiguity.

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?

Explicitly covers both triggers: when the user asks, and proactive offering after an unexpected tool error, a missing capability, a confusing or wrong result, or a workaround. It also states the preconditions for sending (show the exact text first, never include other people's data), leaving nothing to inference.

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