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

readOnlyHint=true already covers the safety profile, and the description adds real behavioral detail beyond it: newest-first ordering, a fixed 25-per-page size, and the fields each row carries. It does not state whether a total count or next-cursor token is returned, so an agent must still call it to learn the pagination contract.

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 core listing contract is front-loaded in the first clause, with ordering, page size and returned fields following in a single dense sentence. The trailing 'Answers:' sentence is mildly redundant but cheap and does add a use case, so nothing is egregious.

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?

With no output schema and four optional parameters, the description supplies what the schema cannot: sort order, page size, and the shape of each row. The remaining gap is pagination mechanics (how to detect the last page, whether a total is included), which an agent can only learn by calling.

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 coverage is 100% and each parameter is documented in the schema, so the schema carries the load. The description's 'narrowed by target, status or OCPI version' largely restates three existing filters, and it omits the cursor parameter entirely even though pagination is the one behavior an agent must get right here.

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?

Specific verb and resource (list conformance runs and charging journeys) plus scope ('on this account'), ordering ('newest first and 25 a page'), the fields returned ('status and pass and fail counts') and the available filters. This distinguishes it clearly from detail-oriented siblings like chargerdojo_get_run_checks or chargerdojo_compare_run without needing to open a schema.

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 closing 'Answers: what ran recently, and how did it go' gives a concrete selection scenario, making it obvious this is the entry-point/recent-activity tool. It stops short of naming alternatives or exclusions (e.g. when to jump straight to get_run_verdict), so it is clear context rather than full routing guidance.

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