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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here and delivers: it discloses the tiered result model (limited free result plus paid upgrade links), the auth mechanism (Authorization: Bearer tt_…, billed in TidyTools credits), and concrete rate limits (1/IP/UTC day, 20 shared pool, 20 global). None of that is recoverable from the annotations or the one-param schema.

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?

Purpose is front-loaded in sentence one, with constraints and pricing following. The telegraphic fragments ('Use for one url.', 'no Apify account needed.') keep it scannable, though the x402/Apify payment sentence is a tangent that dilutes the core routing signal.

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 single-parameter, no-output-schema tool, the definition covers input scope, cost model, auth, and rate limits — enough to call it correctly. What is missing is any hint of which company facts come back, so an agent cannot judge whether the free result is sufficient for its task.

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 description coverage is 100% and the single 'url' parameter is documented as 'One public HTTP(S) URL.' The description reinforces singularity ('Use for one url'), which guards against array-style misuse, but adds no format or validation detail beyond the schema. 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 opening sentence names a specific verb and resource: AI-driven enrichment of public company facts from a single website. It scopes the input ('one website', 'Use for one url'), which separates it from batch-style siblings. It does not, however, distinguish itself from the sibling 'company_enrich' that presumably does a non-AI variant, so an agent must infer that difference.

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?

Explicit positive and negative guidance: 'Use for one url. Not for batch work or unrestricted monitoring.' This tells the agent when the tool is wrong, which is rarer than it should be. The gap is that it never points to the obvious alternative (company_enrich) for the non-AI or the batch case.

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