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

The description explicitly discloses real-world side effects beyond the annotations: 'This CREATES A REAL RECORD and emails a real person.' This adds critical context that readOnlyHint=false and destructiveHint=false do not fully convey, warning the agent about irreversible or consequential actions.

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 compact and front-loaded, stating the core purpose in the first sentence, then adding the critical side-effect warning and usage constraint. Every sentence earns its place without redundant detail.

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 tool with no output schema and asynchronous behavior, the description fully covers what an agent needs to know: the action, the analysis performed, the delivery mechanism (email), and the expected time frame. It also covers the most important prerequisite (user's own email), making it complete for correct invocation.

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 parameters are well-documented in the input schema. The description reinforces the email rule ('Must be supplied by the user, never guessed') but adds little beyond the schema's existing descriptions, so the baseline score of 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?

The description states a specific verb and resource: 'Request Upforge's free technical audit of a website' and clarifies the exact services rendered (PageSpeed/Lighthouse analysis, SEO review, emailing the report). This is unambiguous and easily distinguishable from the sibling tools like request_consultation or get_case_studies.

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 explicit when-to-use guidance: 'only call it when the user has explicitly asked for an audit and given their own email address.' It also states a firm exclusion: 'Never invent an email address to call this.' This goes beyond vague context and gives the agent a clear decision rule.

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