poll_email_test

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

Even though idempotentHint and destructiveHint annotations exist, the description adds valuable behavioral detail: it is an idempotent POST, returns 'pending' if no message, and parses only messages received since the last call. It also explicitly states no auth and no destructive side effects.

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 sentences, front-loaded with the core action, followed by behavior, prerequisites, usage guidance, and safety. Every sentence contributes meaning without redundancy.

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 stateful tool with no output schema, the description sufficiently explains lifecycle behavior, return states, prerequisite ID source, and relationship to sibling tools. No significant informational gap remains.

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% for the single testId parameter, so the schema already carries the semantic weight. The description only repeats that testId comes from create_email_test without adding new parameter detail, meeting the baseline.

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?

Description clearly states it processes the latest received message in an email-test session, distinguishing it from sibling polling tool get_email_test. The verb 'Process' and resource 'email-test session' are specific and non-tautological.

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 tells when to use this tool ('actively trigger parsing after the user reports sending the test mail') and when to use the alternative ('use get_email_test for passive status polling without processing'). This is strong, actionable guidance.

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