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

The description goes beyond annotations by disclosing the side effect of moving the CRM lead to 'replied' when a reply is detected, and clarifies that reply text is not fetched. It also explains the meaning of each status, including edge cases like 'approved' indicating a temporary provider error. This transparency is consistent with the annotations (readOnlyHint=false, openWorldHint=true) and provides significant behavioral context.

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?

The description is fairly long due to the detailed status enumeration, but each sentence serves a purpose: main action, side effect, limitation, and status definitions. It is front-loaded with the core purpose and then provides necessary elaboration. It could be slightly more concise by moving the status list to an output schema or separate reference, but it is not verbose or redundant.

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?

Given the tool's simplicity (one parameter, no output schema) and the presence of annotations, the description is mostly complete. It explains the return value (status) and side effects, and lists all possible statuses with explanations. However, it does not describe the exact output structure (e.g., a JSON object with status and error fields) or error handling for invalid outreach_id. These are minor omissions given the tool's straightforward nature.

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?

The schema has 0% description coverage for the parameter 'outreach_id'. The description does not explicitly explain what outreach_id refers to or its format, though the name is self-explanatory. It does not add meaning beyond the schema, such as examples or validation rules. Given the low coverage, the description should have compensated by describing the parameter, but it only mentions 'one e-mail's status' without linking it to outreach_id. This is a notable gap.

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?

The description clearly states the tool refreshes the status of a single email from Smartlead/Instantly and returns it, also noting a side effect of moving the CRM lead to 'replied' if a reply is detected. The verb 'refresh' and resource 'one e-mail's status' are specific, and the list of possible statuses further clarifies the output. It distinguishes itself from sibling tools like list_email_outreach by focusing on a single email.

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?

The description implies the tool is for checking the status of a specific email but does not explicitly state when to use it versus alternatives. It doesn't mention list_email_outreach or other tools that could list all emails, nor does it provide exclusion criteria. The usage context is inferred from the single-parameter design and the word 'one e-mail', but there is no direct comparison or explicit when-to-use guidance.

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