Dokument abrufen

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

The description discloses the potential truncation of long documents, which is a behavioral trait beyond the readOnlyHint and openWorldHint annotations. It advises using specific searches to mitigate truncation, adding value.

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 concise with three sentences: purpose, usage context, and a behavioral note. It is front-loaded and contains no unnecessary 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?

The description covers purpose, usage, and a behavior warning. While it does not detail the return format, the response_format parameter indicates the output. Given no output schema, it is reasonably complete for a simple retrieval tool.

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 the description does not add new meaning beyond what the schema provides. The note 'from search results' is already in the schema, and no additional semantic information is given.

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 retrieves the full text of a legal document, using the specific verb 'Retrieve' and resource 'full text of a legal document'. It distinguishes from sibling tools, which are for different document categories or history.

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 specifies the tool is to be used after searching, providing clear context. However, it does not explicitly mention when not to use it or provide alternatives, though sibling tools cover different domains.

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