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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful behavioral context by stating the result nests under 'dokumentstatus.dokument,' which is not visible in the schema or annotations. It also clarifies id case-insensitivity (e.g., lowercase accepted), which is a behavioral trait beyond the schema's example.

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 exceptionally concise: two sentences, front-loaded with the main action, and every word contributes. It includes the essential purpose, an example, and the result path without any filler. This is a model of efficient documentation.

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?

For a simple single-parameter tool with rich annotations, the description is nearly complete. It covers what, how, and where the result nests. The only minor omission is a note about possible error conditions or the absence of certain metadata fields, but given the simplicity and the annotation coverage, this is not a significant gap.

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?

The schema provides full coverage for the 'id' parameter with a clear description and example. The description adds extra semantic value by noting that the id can be provided in either uppercase or lowercase ('HD024189' or 'hd024189'), which is not stated in the schema. This enriches the understanding beyond the structural schema.

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's purpose: 'Fetch a single document's full metadata by its id.' It specifies the exact resource (document), the action (fetch), and the scope (single document by id). This clearly distinguishes it from sibling tools like search_documents or recent_changes, which handle multiple documents or searching.

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 implies the usage context: use this when you have a specific document id and need its full metadata. It doesn't explicitly exclude alternatives or name them, but the singular 'by its id' makes the use case clear. The sibling tool names provide context, but the description itself doesn't explicitly compare to alternatives.

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