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

No annotations are provided, so the description carries the full burden. It transparently discloses the per-call fee, payment method, input (domain), and a detailed description of the output structure. It does not mention any side effects, rate limits, or authorization needs, but the tool appears to be a read-only assessment with no destructive 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 moderately concise, covering cost, input, output details, and differentiation from siblings in a few sentences. It is front-loaded with the most important info (cost and payment). Could be slightly more concise, but every sentence serves a purpose.

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 that there is no output schema, the description does an excellent job explaining the return value: a structured judgment with specific fields (company description, category, audience, business model, market, language, analyst take, sales hook, confidence ratings, evidence quotes). It also covers cost and payment method completely.

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?

Only one parameter 'domain' exists, and the schema already provides a description and example. The tool description adds context: the domain is from a company's homepage, and the output is a structured judgment. Schema coverage is 100%, so baseline is 3; the description adds a bit more meaning by explaining what the domain is used for.

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's purpose: 'Get an AI analyst's read on a company from its homepage.' It specifies the verb (assess), the resource (company via domain), and the output format (structured judgment). It also distinguishes from sibling tools like /enrich and /report by calling itself the 'qualitative complement.'

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 clear usage context: cost ($0.10 per call), payment method (x402 USDC on Base), and that no account is needed. It briefly contrasts with siblings ('qualitative complement to /enrich and /report'). However, it does not explicitly state when not to use this tool or list prerequisites beyond having a domain.

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