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

The readOnlyHint annotation already establishes this as a safe read operation, and the description adds no behavioral concerns such as authentication, rate limits, or side effects. It does add the useful detail that results are grouped by module and include counts, but no additional behavioral traits beyond that.

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 sentence delivers the core purpose, the grouping behavior, and the check-count detail with zero filler. It is front-loaded and appropriately sized.

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 read-only listing tool with no output schema, the description conveys the essential return shape: conformance suites grouped by module with check counts. It is sufficiently complete, though it could have briefly noted when to prefer this over listing OCPI versions.

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 fully documents the only parameter, version, with an example ('2.2.1'), and the description does not need to repeat it. The description does not add meaning beyond the schema, but with 100% schema coverage the baseline of 3 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 states a specific resource ('OCPI conformance suites') and verb ('List'), plus the grouping by module and check counts. This clearly distinguishes the tool from siblings like chargerdojo_list_ocpi_versions and chargerdojo_list_journey_templates without needing to open schemas.

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 when to use it: when the agent needs to see which conformance suites are available to run and how large they are. However, it does not explicitly say when not to use it or mention alternatives such as chargerdojo_list_ocpi_versions or chargerdojo_list_journey_templates.

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