Analyze URL or Site

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

Description adds API endpoints and the brand requirement, but behavioral traits like read-only, idempotent are already covered by annotations. No additional context about rate limits or auth.

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?

Single sentence, concise and front-loaded with purpose. Could benefit from bullet points for clarity, but 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?

Given comprehensive annotations and output schema, description is reasonably complete. It explains the two modes and a key dependency. Minor gaps like output format are covered by output schema.

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 has 100% coverage, but description adds valuable constraints: 'brand' required with 'site', and 'site' vs 'url' are mutually exclusive. This goes beyond schema descriptions.

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 specifies 'domain/site keyword discovery' with two modes (site and url), making the purpose clear. However, it does not explicitly distinguish from sibling tools like 'discover_keywords' which may overlap.

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?

Provides guidance on when to use 'site' vs 'url' and notes that 'brand' is required with 'site'. But no explicit when-not-to-use or comparison to sibling tools.

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