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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds genuinely useful behavioral context beyond them: the fetch is SSRF-safe, only public pages are touched, and there is a $0.03 USDC x402/Solana charge per successful call. It does not cover rate limits, failure modes, or timing, keeping it from a 5.

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 field list is front-loaded and dense, with safety and pricing details following in short sentences. The long enumeration is justified because it doubles as the return-value description, though it is slightly list-heavy.

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 one-parameter, read-only tool with no output schema, the description adequately covers what comes back (field list), safety (SSRF-safe), cost (x402) and an alternate transport. Minor gaps remain around output structure and partial-failure behavior.

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?

With one parameter at 100% schema description coverage, the schema already explains that a URL or bare domain is accepted. The description adds nothing about accepted formats, redirect handling, or error cases, so the baseline 3 applies.

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 names a specific resource ('Company profile from its own website') and enumerates exactly what is extracted (name, logo, socials, emails/phones, JSON-LD, OG/Twitter, RDAP basics), which implicitly distinguishes it from narrower siblings like opengraph or contact_extract. However, it never names a sibling or states an explicit boundary, so it falls short of a 5.

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?

Usage is only implied: the reader infers this is the right tool when they want a broad company identity snapshot from a URL. There is no statement of when not to use it, no named alternatives for sub-tasks like email-only extraction, and no prerequisites beyond the schema's 'public http(s) only'.

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