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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing pagination (30 per page, pages 1-10, total count), that data comes through a rendering residential proxy, and the exact billing model: $0.02 USDC per successful call via x402 on Base/Solana/Arc with failed calls not charged. Cost and charging semantics are exactly the kind of context annotations cannot convey.

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 purpose and data fields are front-loaded, followed by pagination and the pricing/payment sentence. Sentences are dense but every one carries information; the long comma-separated field list is the only mildly bloated part and largely duplicates the output schema.

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?

With an output schema and readOnly/openWorld annotations present, the description supplies the missing operational context: pagination bounds, total count, data source/proxy, and payment terms. Only minor gaps remain, such as how the x402 payment handshake is initiated or whether auth is required before paying.

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 coverage is 100% so the baseline would be 3, but the description adds result-shape context not in the schema: 30 results per page and the page 1-10 ceiling, plus that price is in INR with display text and per-sq-ft. The schema already documents city examples and type defaults, so the added value is incremental rather than decisive.

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 names the specific resource (MagicBricks India homes for sale or rent in a city) and enumerates the exact fields returned, so an agent knows precisely what data to expect. It stops short of explicitly distinguishing itself from the closest sibling, realestate_squareyards_india, though the magicbricks.com domain mention implicitly does that.

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?

Usage is implied rather than stated: an agent can infer this is the tool for India property listings by city, with page 1-10 limits. There is no explicit 'use this instead of X' guidance or prerequisite/key requirements, even though an India-focused sibling (squareyards_india) exists.

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