get_permits_for_parcel

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

With no annotations provided, the description carries the full burden. It correctly indicates a read operation ('Fetch') and describes the returned fields. However, it does not explicitly state idempotence, authentication needs, or potential performance impacts, leaving some gaps.

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 consists of exactly two sentences, each adding distinct value. No redundant information, and the most critical details (purpose, filter, return fields) are front-loaded.

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 the tool's simplicity (3 params, output schema exists), the description covers essential aspects: what the tool does, how to filter, and what is returned. It does not mention the default limit or error conditions, but the presence of an output schema somewhat reduces the need for detailed return description.

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 coverage is 0%, so the description must compensate. It explains the 'apn' parameter (by APN) and the 'status' parameter with allowed values listed. The 'limit' parameter is not mentioned, but since it has a default value, the omission is partial. Overall, it adds significant meaning beyond the bare schema.

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 clearly states the verb 'Fetch' and the resource 'building permits for a parcel by APN'. It lists the filter parameter and return fields, differentiating it from sibling tools like get_violations_for_parcel or get_overlays_for_apn.

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 provides clear context for when to use this tool (to fetch permits by APN with optional status filter). However, it does not explicitly state when not to use it or mention alternative tools for related data.

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