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

Annotations already convey mutability (readOnlyHint=false) and non-idempotence. The description adds that only 'website' type is supported via MCP and mentions file upload restriction, but does not elaborate on side effects (openWorldHint=true) or other behavioral traits like 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?

Two sentences with no wasted words. Essential purpose is front-loaded, and the exclusion note is concise. Every sentence adds value.

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?

The description covers core purpose and key constraint (no file uploads), but given 7 parameters and nested arrays, it omits guidance on using 'links' vs 'url' and the meaning of 'relative_links_limit'. Output schema exists but isn't referenced. Adequate but not fully complete.

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 coverage is 57%. The description clarifies the 'type' enum (only website) and implies url is primary, but doesn't explain 'links', 'description', or 'relative_links_limit'. It adds some value over the schema but not enough to compensate fully for uncovered parameters.

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 states 'Add a website (URL-scraped) document to a knowledge base' with a specific verb and resource, clearly distinguishing from file upload tools. Sibling tools like create_knowledgebase or update_document are distinct.

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 says when to use (URL-scraped documents) and when not to (file uploads must use dashboard or multipart call). Provides clear context and alternative channels, helping the agent avoid misusing this tool for file uploads.

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