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

With no annotations provided, the description carries the full behavioral burden. It discloses that the operation mutates state ('Saves to the agent'), costs 15 credits, takes 60-180 seconds, and requires prior approval. This is strong behavioral transparency for a paid write operation, though it could further clarify whether existing saved scan data is overwritten.

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, covering scope, side effect, cost, and precondition in two dense sentences. Every sentence adds operational value, and there is no redundant or filler content.

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 paid, state-mutating operation with no annotations and no output schema, the description covers the most important operational concerns: prerequisites, cost, duration, and persistence. However, it leaves the three required parameters under-specified and does not describe what happens after the scan completes or what return value the agent should expect.

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 input schema has 0% description coverage, and the description does not explain the meaning of 'id', 'company_name', or 'company_website' as distinct parameters. It implies company_website is the site to crawl, but leaves 'id' and 'company_name' ambiguous, which is a significant gap given the agent must provide all three required fields.

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 action ('Crawl 15+ pages'), a specific resource ('the agent's company website'), and specific outputs ('people, contacts, pricing, social links'). It also states the side effect of saving to the agent, which clearly distinguishes it from preview-only or quick-scan sibling tools.

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 explicitly provides a precondition: 'Only call after preview_deep_scan and user approval.' This tells the agent exactly when it is appropriate to invoke this tool and references the sibling that must precede it, leaving no ambiguity.

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