permits.history

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

No annotations provided, so description carries full burden. It discloses that coverage varies by jurisdiction (top-100 metros complete, smaller may be empty) and lists returned fields. Does not explicitly state read-only, but implied. Good context for an agent.

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?

Five sentences, each adding unique value: purpose, field list, positive usage, negative usage, coverage caveat. Front-loaded with purpose. No fluff.

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?

Covers purpose, usage, field details, and coverage limitations. Lacks mention of pagination or default ordering, but given the tool's simplicity, it is fairly complete. No output schema, so description of return values is adequate.

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%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions; it only mentions parcel_id implicitly. No additional value.

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?

Clearly states it returns a timeline of permits for a parcel, listing specific fields. Distinguishes from sibling 'parcel.search' by saying not to use for finding properties with permits across a market.

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?

Explicitly states when to use (construction activity, renovations, planned work) and when not to use (finding properties with permits across a market, deferring to parcel.search). Also provides coverage caveat.

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