get_next_charge_onboarding_candidate

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

No annotations are provided, so the description carries the burden. It states it returns one candidate (non-mutating), but does not disclose whether the call has side effects (e.g., marking the candidate as 'in progress') or any other behavioral traits beyond the return.

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, front-loaded sentence with no unnecessary words; every word adds value.

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 getter tool with an output schema, the description is minimal but functional; however, it lacks explanation of the priority order and the optional db_path parameter, which reduces completeness.

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 has 1 parameter (db_path) with 0% description coverage; the description does not mention or clarify the parameter's purpose, leaving the agent with no guidance on what to provide.

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 uses a clear verb 'Return' and specifies the resource 'charge-onboarding candidate' with qualifiers 'single highest-priority unresolved', making the tool's purpose precise and distinct from sibling tools like 'scan_charge_onboarding_candidates' or 'list_charge_onboarding_queue'.

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 indicates it returns the highest-priority unresolved candidate, implying use in a processing loop, but it does not explicitly state when to use this tool over alternatives like 'list_charge_onboarding_queue' or 'scan_charge_onboarding_candidates', nor does it explain the priority mechanism.

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