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

The description portrays this as a purely informational read operation ('Returns... information'), but the annotations set readOnlyHint=false and destructiveHint=true, implying potential side effects or destructive behavior. This is a direct contradiction; the description fails to disclose any behavioral context and actually misleads about the tool's safety profile.

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?

Two sentences with dense, relevant content and no filler. The list of coverage areas is comprehensive but compact, and the purpose statement is 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?

The description provides a rich overview of what the tool returns, covering multiple relevant dimensions for Philadelphia restoration. However, the contradiction with annotations (destructiveHint) leaves a significant gap in understanding side effects, and there is no mention of response format, which is only partially mitigated by the clear content list.

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?

Input schema covers both parameters exhaustively (100% coverage), including enums and descriptions for info_type and neighborhood. The description adds no additional parameter-level detail beyond listing broad content areas, so it does not exceed the schema baseline.

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 tool's function: returning Philadelphia-specific local information for damage restoration. It lists specific content areas (housing stock, damage patterns, flood risk, etc.) and distinguishes it from sibling tools like assess_damage and estimate_cost by focusing on local context rather than assessment or cost.

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 use: when agents need neighborhood-aware guidance for Philadelphia homeowners. It does not explicitly name alternatives or state when not to use this tool, so it stops short of full differentiation.

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