fetch_document

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

Without annotations, the description discloses key behaviors: uses authenticated browser session to bypass CDN access controls (security/network context), and returns full text and page count (output). It does not mention rate limits or side effects, but the tool is read-only and non-destructive, so the disclosure 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?

Three concise sentences with no superfluous information. The first sentence states the core purpose, followed by usage instructions and a brief output summary. 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?

Given the tool's simplicity (one required param, no output schema), the description fully covers what the tool does, what input is needed, and what output is returned. No additional context required.

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?

Only one parameter ('url') with schema specification of type string and format uri. The description adds meaning by stating it should be a URL from 'get_knowledge_base', which guides the agent on the source and validity of the input. This compensates for the 0% schema description coverage.

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 ('Fetch and extract text') and the resource ('Tijori Finance document (PDF)'), specifying it returns full text and page count. It distinguishes from sibling tools by its focus on document extraction.

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 instructs to 'Pass a URL returned by get_knowledge_base', providing clear context on when to use this tool. Also mentions using the authenticated browser session, implying it handles access control automatically. No exclusions or alternatives given, but sufficient for the use case.

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