migration_area_baidu

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds result limits (top 100, or all if fewer) and ratio definitions, but includes an internal inconsistency (return says top 50 while earlier says top 100), reducing clarity. No contradiction with 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 fairly compact but includes redundant title lines and an extraneous URL. The param/return structure is clear, but the repeated '百度地图慧眼-百度迁徙' and the 100 vs. 50 inconsistency add noise. It earns its place but could be streamlined.

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?

It covers essential retrieval details (area, indicator, date, output type) and includes the data source URL. However, the top-100 vs top-50 ambiguity, lack of column details beyond ratios, and absence of any mention of pagination or sibling differentiation leave gaps for a data tool with no output schema.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning, acceptable values (move_in/move_out), date format and range, and the requirement for full area names. This is strong parameter-level guidance 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 identifies the tool as retrieving Baidu Migration area details (incoming/outgoing) for a specified area, indicator, and date, and it explains the proportion metrics. However, it does not explicitly differentiate from sibling tools like migration_scale_baidu, relying on the title and parameter docs to convey the exact resource.

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 usage constraints (full-name requirement for area, valid date range, indicator values) but does not state when to use this tool versus alternatives. No explicit exclusions or references to sibling tools are given, so the agent must infer suitable use from context.

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