ghl_email_verify

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

Annotations are sparse (readOnlyHint false, destructiveHint false). The description does not explain the side effects (e.g., potential charges, which are hinted in the schema but not repeated). It mentions 'lc-email.readonly' OAuth scope, which contradicts the readOnlyHint false annotation, creating confusion. No disclosure of rate limits or idempotency.

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 short but includes unnecessary internal details like 'Version header: v3; source: v3/email-isv-v3.json' that are irrelevant to an agent. It could be more concise by omitting these and focusing on the core action. The structure is acceptable but lacks front-loading of the most critical information.

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 (2 params, no output schema) and the presence of annotations, the description is incomplete. It does not explain the expected output, what happens on success/failure, or the meaning of the 'type' parameter (email vs contact). The charge implication from the schema is not reinforced.

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 schema provides descriptions for all parameters. The main description adds no parameter information. Per guidelines, baseline is 3 when schema coverage is high and description adds nothing. However, the body's schema description is generic, and the main description could have clarified the 'type' enum options.

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 states 'Email Verification' and 'Verify Email', clearly indicating a verb and resource. It distinguishes itself from sibling tools as no other tool focuses on email verification. However, the description lacks details about the scope of verification (single email vs batch) and includes non-helpful internal details like version headers.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions under which it should or should not be used. Sibling tools are numerous but unrelated, so no differentiation is offered.

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