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

Description adds context beyond annotations: async nature ('takes a few minutes'), polling requirement, and free usage limits. Annotations (readOnlyHint=false, openWorldHint=true) align with starting an external research run. No contradictions.

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?

Three sentences, front-loaded with action, no redundant words. Every sentence adds value: action, async flow, constraints.

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?

Explains the async flow and return values (id, token). Geographical and platform limits are stated. Lacks details on error handling or id format, but sufficient for a simple 1-param tool without 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?

Schema description already covers the parameter fully (100% coverage: URL type, platform constraints). Tool description repeats the same info without adding extra meaning or format details. Baseline 3 is appropriate.

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 'Start a Flatscope research run' on a specific resource (UK Rightmove or Zoopla listing). It distinguishes from sibling tools like 'get_flat_analysis' (polling) and 'about_flatscope' by describing the async initiation process and constraints.

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?

Provides clear when-to-use: Rightmove/Zoopla listings in England/Wales. Explicitly excludes OnTheMarket. Tells user to poll 'get_flat_analysis' with returned id/token. Mentions free first few runs, implying usage limitations.

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