Read a Wikisource page

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

Only mentions truncation via max_chars. No annotations present, and description omits details on error handling (e.g., missing page), request limits, or encoding, placing full burden on the description.

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 concise sentences that front-load purpose and key constraint (truncation). 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?

Adequate for a simple fetch tool with full schema coverage. Lacks mention of error states or handling of edge cases (e.g., non-existent titles), but sufficient given the narrow scope.

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 has 100% coverage with clear parameter descriptions. The description adds minimal extra value ('from search_wikisource' for title context) but does not deepen understanding of parameter behavior beyond schema defaults.

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?

Clearly states the verb 'Fetch', resource 'plain text of a Wikisource page', and specific context 'by title (from search_wikisource)', distinguishing it from siblings like search_wikisource and other fetch tools.

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 links to search_wikisource for obtaining the title, implying the intended workflow. However, lacks explicit when-not-to-use or comparisons with similar fetch tools from other sources.

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