list_mileage

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is already covered. The description adds no behavioral context beyond that—no pagination behavior, default ordering, authorization requirements, or response shape—making it purely redundant.

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 words is under-specification rather than effective conciseness. It omits all necessary context and front-loads nothing useful for an agent parsing the definition.

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 six parameters and no output schema, this description is completely inadequate. It does not state what mileage records represent, how the filters combine, or what the list returns, so an agent cannot reliably determine whether this tool fits a request.

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 provides descriptions for all six parameters (to, from, limit, offset, status, tutor_id), achieving 100% schema coverage, so the baseline of 3 applies. The description itself adds no parameter semantics; the schema carries the meaning.

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 'List Mileage' is a tautology—it merely restates the tool name. It does not specify what mileage records are, what domain they belong to, or how this tool differs from sibling list tools such as list_expenses or list_payments.

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?

There is no guidance on when to use this tool versus alternatives. No contextual cues, exclusions, or mentions of sibling tools or filters that would help an agent select it appropriately.

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