freeagent_create_mileage_expense

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

With annotations providing no supportive hints (all false), the description carries the burden and excels. It discloses that the claim value is computed by FreeAgent, that ratePence/cumulativeMilesYTD are advisory only, and that distance lookup requires API keys. This goes well beyond the structured data.

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 description is compact, front-loaded with the core action, and every sentence contributes critical information. It avoids fluff and redundancy while conveying complex behavioral nuances in two paragraphs.

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?

Given 11 parameters and no output schema, the description covers all essential usage aspects: input modes, distance computation, rounding behavior, and the distinction between advisory and filed values. No critical gap is apparent for an AI agent to select and invoke this tool 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?

Despite 100% schema coverage, the description adds significant semantic value by explaining the exclusive-or relationship between origin/destination and manualMiles, the effect of roundTrip, and the advisory nature of ratePence/cumulativeMilesYTD. This synthesis is not obvious from the schema alone.

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 specific verb-resource pair ('Create a mileage expense in FreeAgent') that clearly identifies the tool's function. It implicitly distinguishes itself from the sibling 'create_expense' by focusing specifically on mileage, and the name reinforces this. No ambiguity exists.

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 clearly instructs when to use origin+destination versus manualMiles, and explains the roundTrip flag. It does not explicitly mention when to prefer this over freeagent_create_expense, but the context is clear enough for mileage-specific scenarios. A slight exclusion note would elevate it to 5.

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