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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes far beyond by disclosing the SSRF guard rules (https only, no redirects, public addresses only, size/time caps), the generic failure message and the absence of a bypass, the async parse→chunk→embed pipeline, the shared per-user import allowance, and the embedding-key requirement.

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?

Front-loaded with the core action and mechanism, and the dense clause runs (async pipeline, SSRF guard) each carry operational value rather than filler. It is long but justified by the tool's complexity, though slightly run-on.

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?

An output schema exists, so return values need not be described. The description covers prerequisites, failure modes, async semantics, and constraints, leaving no material gap for correct invocation.

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%, so url, kb_id, and title are already documented in the schema. The description reinforces that only https schemas are accepted and that the KB must be owned, but adds little parameter detail beyond the schema baseline.

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?

States a specific verb and resource ('Add a document to a knowledge base'), the input mechanism (https URL), and the server-side behavior (fetch, extract, ingest asynchronously). It even names the sibling it differs from via the 'Add from URL' analogy, so an agent can distinguish it from findagent_add_kb_document without reading either schema.

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 routes to the alternative: 'To paste text instead use findagent_add_kb_document.' It also states the precondition for success ('Requires the KB to have an embedding key bound, or the document will not ingest') and the constraint that the KB must be owned, giving clear when/when-not guidance.

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