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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds nothing beyond that — no note on what a document contains, whether access is permission-gated, or any rate/scope caveat. With annotations carrying the load, a low score reflects the absence of any supplementary behavioral context.

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?

A single short sentence with no filler, and the key identifier ('by ID') is front-loaded. It is efficient, though the brevity edges toward under-specification rather than true concision.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile, making the minimal description roughly viable for a simple by-ID lookup. Still, nothing tells the agent how this differs from related document tools or what access assumptions apply.

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% and two of the three parameters are enums with inline explanations, so the schema fully documents inputs. The description contributes no additional meaning about documentId, fields, or format, which is exactly the baseline-3 case.

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?

States a specific verb and resource ('Retrieve a document by ID'), which is unambiguous as an operation. However, it does not differentiate from close siblings such as glpi_get_document_item (the link between a document and an item) or glpi_list_documents, leaving the agent to infer the boundary.

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?

There is no when-to-use guidance and no mention of alternatives, even though glpi_list_documents and glpi_get_document_item are adjacent candidates an agent could confuse with this one. The description simply restates the operation without routing the agent.

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