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

Annotations mark this as a non-read-only, non-idempotent write, and the description adds genuinely new behavior: the message is delivered to a human team, it requires explicit user consent, and it does not consume the daily quota. The rate-limit and consent semantics go well beyond what the structured fields convey.

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-loads the action and resource, then moves through routing triggers, frequency limit, and consent requirement in three dense sentences with no filler. Every clause carries a distinct operational instruction.

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 an output schema present, return values need no explanation, and the description covers the remaining gaps an agent would face: consent requirement, frequency limit, quota exemption, and delivery destination. Nothing needed to invoke this 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 description coverage is 100%, so kind, about, and message are already fully documented including the enum values and length bounds. The description reinforces that the message should be the user's own words, but adds no format or syntax detail beyond the schema; 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 (send) and resource (the user's feedback to the Pressure Atlas team), then enumerates the accepted kinds. This clearly demarcates it from all sibling tools, which are read-only data retrieval operations.

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 lists trigger conditions (user wants something the tools don't do, hits a limit, is confused or frustrated, expresses like/dislike), states the frequency ceiling (at most once per conversation unless the user raises it), and mandates asking the user first. Both when-to-use and when-not-to-use are covered.

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