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

With no annotations, the description carries the full burden and largely succeeds: it defines the tier vocabulary, explains that ambiguous names return candidates rather than a single record, clarifies that a null costLocal is not a number and null status means 'not recorded', warns figures may be provisional, and offers a verification path via record signature. Auth requirements and any rate limits are unaddressed, which keeps it short of a 5.

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?

It is front-loaded with the most important information, but the trust-tier vocabulary is stated twice (once for 'tier', once for 'permit status') and the sourcing/dated/provisional caveats are spread across several short sentences that could be consolidated. Adequate but not tight.

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?

There is no output schema and no annotations, so the description must explain both the return shape and the behavioral caveats; it does both, including null handling and the provenance follow-up. The main omission is any statement about permissions or error behavior, which is minor for a single-parameter read tool.

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 description coverage is 100% for the single 'trail' parameter, so the schema already documents slug-or-name input. The description adds only marginal semantics beyond that — the note that ambiguous names return candidates — so the baseline 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?

States a specific verb+resource ('Sourced permit fee for a named trail') and enumerates the returned fields (costLocal, tier, issuer, source URL, read-date), so an agent knows this returns fee/status data rather than trail geometry or itinerary planning. It does not explicitly contrast itself with get_trail or plan_permits, but the resource is narrow enough to be distinguishable.

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?

Usage guidance is mostly about output handling ('Do not quote reported-secondary or unverified as official') rather than when to call this tool versus siblings. It does point to one alternative for verification ('can be verified with get_provenance'), but gives no condition for choosing get_permit over get_trail or plan_permits.

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