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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond them by disclosing what the read returns — rollout (who receives replies), quiet period, and their `sources` — useful because there is no output schema.

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 front-loaded sentence with no filler, and the returned concepts are named immediately. Slightly compressed jargon ('rollout', 'sources') is used without explanation, 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?

For a single-parameter read-only getter with no output schema, the description covers the essentials by naming the settings returned. A note on whether an unconfigured mailbox returns defaults or errors would close the remaining gap.

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 100% and the mailboxId property already explains where the id comes from (add_support_email or get_setup_status). The description adds no further semantic detail about the parameter, 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 verb-and-resource pair: read the reply configuration ('how Aide answers a support mailbox'), naming rollout and quiet period. It is distinguishable from get_support_email in practice, but the description never explicitly contrasts with that sibling or with update_support_email_settings, so the separation relies partly on the tool name.

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 only implied: it is the read counterpart to update_support_email_settings, which the agent must infer from the near-identical name. There is no explicit 'use this before updating' or 'use get_support_email instead for X' guidance.

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