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

Annotations already declare openWorldHint=true and idempotentHint=true, and the description adds genuinely useful context the schema doesn't: the $0.03/call cost and the hybrid LLM+deterministic execution model. It doesn't explain the unexpected readOnlyHint=false or any rate/latency behavior, but the pricing disclosure is meaningful value beyond structured fields.

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?

Two tight sentences, with the core purpose and cost front-loaded before the routing guidance. No wasted words.

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?

An output schema exists, so return values need not be described, and the payment path is covered in the x_payment schema. Cost and sibling routing are provided, though the description could say more about input limits (page/PDF size, schema complexity) for a service with a per-call fee.

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%, so the schema already documents url, schema, x_payment, and instructions fully. The description reinforces 'your own schema' and 'any URL/PDF' but adds no syntax or format 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?

States a specific verb+resource ('Fill YOUR JSON schema from any URL') and adds the mechanism ('hybrid LLM + deterministic canonicalization'). It also names the sibling tools it is not (enrich_company, jp_company_profile), so an agent can distinguish it without inspecting schemas.

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?

Explicitly states when to choose it ('when you have your OWN JSON schema to fill from any page') and names the alternatives for the company-profile case. The routing condition is unambiguous.

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