drill_down_local_analysis

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context about output being Markdown and focusing on foot traffic/commercial/education, but does not disclose limitations like data coverage or behavior for missing neighborhoods. It is adequate given the annotations.

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 extremely concise, with two sentences in both English and Japanese. It front-loads the main purpose and includes no filler. Every word is necessary.

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?

Although the description names content areas and mentions Markdown output, it omits critical details: the actual output structure, alternative export formats, how to use the focus parameter, and the meaning of the analysis. An agent cannot fully understand the tool's response without additional documentation.

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 80%, so the schema already documents most parameters. The description adds marginal value by hinting at the analysis content but is redundant with focus enum and does not clarify the exportFormat default (which is json, not markdown).

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 performs drill-down local analysis at the block/neighborhood level and lists included content (foot traffic, commercial, education). It distinguishes from siblings like generate_area_report by specifying granularity, but does not explicitly contrast alternatives.

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 no guidance on when to use this tool versus siblings or prerequisites. It does not explain that neighborhood is optional or that prefecture can be inferred. An agent lacks context for selection.

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