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

The readOnlyHint annotation already declares the safe read profile, and the description adds meaningful context beyond it: schedules are set in the app on the Automate plan, and the response covers cadence, pause state/reason, next run, and last-run outcome. It does not cover authentication requirements or error behavior, but adds useful operational detail.

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?

Two sentences, front-loaded with the core action and followed by a practical question-based framing. There is no filler, and the plan/configuration note earns its place by clarifying why the operation is read-only.

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 one-parameter read tool with annotations and no output schema, the description is complete: it explains what is read, what the result covers, and the plan context. An agent has enough information to select and call it correctly.

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%; the targetId parameter is documented in the schema as coming from chargerdojo_list_targets. The description reinforces that this reads one target but adds no syntax or format detail beyond the schema, so 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 verb (Read) and resource (the recurring run set on one target), then enumerates the returned facets: cadence, paused/on state, next run, and last run result. This clearly distinguishes it from run-level siblings such as chargerdojo_list_runs or chargerdojo_get_run_verdict.

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?

It gives clear context for when to use it: to answer whether an endpoint is tested on a schedule and whether its last scheduled run passed. It also notes schedules are configured in the app on the Automate plan, implying this tool is for reading rather than editing, though it does not explicitly name alternative tools.

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