Dokument abrufen

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

Discloses truncation behavior for long documents, which is beyond the readOnlyHint and openWorldHint annotations. Does not contradict annotations. Could further detail what constitutes 'long' or response size limits, but current disclosure is helpful.

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?

Extremely concise: three sentences covering purpose, usage, and a notable limitation. No wasted words. Front-loaded with the main action.

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 full schema and annotations, the description covers the main purpose, usage context, and a key limitation. Output schema not provided but return values (full text) are implied. Missing specifics on truncation threshold or error handling, but adequate for typical use.

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 covers all 3 parameters (100% coverage). The description adds value by noting that dokumentnummer comes from search results, aiding proper use. The other parameters are well-described in schema, so extra details are not needed.

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 'Retrieve full text of a legal document' with specific verb and resource. It positions this tool as a post-search action, distinguishing it from sibling search tools for different categories (e.g., ris_bezirke, ris_bundesrecht).

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 'Use this after searching to load the complete text' providing clear usage context. Adds caution about truncation for long documents and suggests narrowing searches. Lacks explicit when-not-to-use or alternatives, but siblings cover different document types, so implicit.

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