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

With no annotations, the description carries the full behavioral burden. It adds useful context by listing report contents and signaling a paid/subscriber ('PRO') tier, but it does not explicitly state read-only behavior, authentication requirements beyond the vague 'PRO' label, rate limits, or output format.

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 and front-loads the core purpose after the 'PRO.' marker. It contains little waste, though the isolated 'PRO.' token is ambiguous and slightly reduces clarity.

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?

For a report tool with no output schema and no annotations, the description gives a helpful list of return contents. However, it leaves out important context such as subscriber/authentication requirements, behavior relative to sibling tools, and response format details.

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 50%: the access_token parameter is documented in the schema, while zip is undocumented there. The description reinforces that the report is for a ZIP, but it adds no syntax, format, or validation details for either parameter.

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 states a specific resource and scope: a full NFIP claims report for a ZIP, including paid amounts by year, average claim, flood zones, and named events. It is clear what the tool does, but it does not differentiate itself from siblings like flood_history or compare_zips.

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 explicit guidance on when to use this tool instead of flood_history or compare_zips, nor when not to use it. The only implied usage is that it applies to a single ZIP, while 'PRO' hints at subscriber access but does not explain prerequisites or alternatives.

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