Domain Knowledge

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

Discloses read-only behavior by describing inspection of previous visit data. No annotations are provided, but the description implies no destructive actions. It lacks details on rate limits or permissions but is adequate.

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 sentences, front-loaded with purpose, no extraneous information. Every word contributes to clarity.

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 one optional parameter, no output schema, and no annotations, the description fully covers the tool's purpose and usage. It explains the parameter behavior completely.

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% for the single parameter. The description adds 'Pass no domain to list all known domains,' which mirrors the schema's 'Omit to list all' but is not redundant. Minimal added value beyond schema.

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 clearly states the verb 'Inspect' and the resource 'what Leapfrog has learned about a website from previous visits'. It lists specific data shown (stealth tier, etc.) and differentiates from sibling tools by focusing on domain knowledge inspection.

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 clear context: 'Pass no domain to list all known domains'. While it doesn't explicitly state when not to use or mention alternatives, the instruction is sufficient given the tool's unique purpose among siblings.

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