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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the write/safety profile is covered. The description adds useful scope behavior ('seeds belong to the account, not one project'), but says nothing about reversibility, the confirm guard referenced in the schema, or what happens on a duplicate seed.

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?

Three compact sentences with zero waste: purpose first, then the account-scope constraint, then the sibling routing. Nothing is buried or repeated.

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?

No output schema exists, so the description must stand alone, and it covers purpose, scope, and alternative adequately for a simple add operation. It stops short of describing duplicate handling or when the confirm flag is expected, which are the only meaningful 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%, so all three parameters (app_id, address, confirm) are already documented in the schema itself. The description adds no parameter-level detail beyond the Gmail-vs-manual distinction, so the baseline 3 is appropriate.

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+resource ('Add a seed inbox') and immediately scopes it to manual-check inbox placement tests (Outlook, Yahoo), which cleanly separates it from the Gmail/automatic sibling. An agent can identify this tool without opening any schema.

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 routes to the alternative: 'For a Gmail seed whose results are read automatically, use get_seed_connect_link instead.' The condition that selects this tool (results the owner checks by hand) and the condition that selects the sibling are both stated.

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