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

No annotations exist, so the description carries the full burden. It mentions 'start indexing it' but does not disclose side effects, prerequisites (e.g., valid chatbot_id), whether URLs already indexed are handled, asynchronous behavior, or permissions required.

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?

The description is brief and front-loaded with the core action. The second sentence ('Provide a single page or site URL') is slightly redundant but not harmful. Overall it is concise with 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 no output schema, the description does not explain what the tool returns after adding a source (e.g., a source ID or confirmation). It also does not mention whether the indexing is immediate or asynchronous, or any success/failure signals. Missing important contextual information for an agent.

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?

Parameter descriptions in the schema cover 100% of parameters. The description adds only a minor clarification that the URL can be a single page or site, and that the title is optional. This provides marginal added value beyond the schema, earning the baseline score.

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 tool adds a website knowledge source by URL and indexes it. The verb 'add' and resource 'knowledge source' are specific and distinct from sibling tools (e.g., list_sources, recrawl_source).

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?

The description indicates to provide a single page or site URL, but lacks explicit guidance on when to use this tool versus alternatives like list_sources (to check existing sources) or recrawl_source (to reindex). No exclusion criteria or context for use given.

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