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

The annotations already indicate readOnlyHint=true, and the description aligns with that. It adds useful behavioral context by disclosing that the tool explains which tools are open and which require an API key, which is beyond the read-only property signal.

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 efficient sentence fully conveys the tool's purpose and scope. There is no wasted text, and the wording is front-loaded with the core intent 'Explain what this server can do'.

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 no-parameter informational tool, the description is complete: it states what the output conveys (server capabilities and access requirements) and the readOnlyHint annotation covers side-effect transparency. Nothing essential is missing.

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 input schema is empty with full coverage, so parameter semantics are inherently satisfied. The description doesn't need to document any parameters, and the baseline for a zero-parameter tool is appropriate.

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 names a specific verb, 'Explain', and a specific resource: what 'this server can do' and access requirements. It clearly distinguishes the tool from siblings like chargerdojo_list_ocpi_versions or chargerdojo_get_ocpi_version, which list versions rather than describing overall server capabilities.

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 implicitly frames this as the starting-point tool for understanding the server and its access requirements. It gives clear context for when to call it, though it does not explicitly say when not to use it or name alternatives as competitors.

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