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

No annotations provided, so description carries full burden. It explains that AYO scans the website, indexes into AYA, returns immediately, and entry appears within ~30s. It does not mention potential side effects or permissions needed, but covers the main behavior well.

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?

Description is slightly lengthy but each sentence provides value. It is front-loaded with the action and includes necessary details. Could be more concise, but no dead weight.

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 the tool has one parameter, no output schema, and no nested objects, the description covers purpose, usage, behavioral timing, and constraints comprehensively. No gaps for effective agent use.

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) with 100% schema description coverage. The description adds a usage example (e.g., acme.com) but repeats the schema's description. With high coverage, baseline is 3; description adds minimal extra value.

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?

Description clearly states the action (Add a company) and resource (to AYA via AYO). It distinguishes from sibling tools by specifying when to call: when search_companies/get_company_details did not find the company.

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 call (when research surfaces a real business not found in registry) and when not to call (only submit real companies, not guesses). Provides clear context for selection.

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