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

Annotations already declare read-only and non-destructive behavior; the description adds valuable context: 'No login, no browser, no proxies' clarifies auth/infrastructure requirements, and pricing is disclosed. It does not detail rate limits or query behavior, but annotations cover the 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?

The description is compact: one principal sentence covering purpose and source, plus a brief note on technical requirements and pricing. Every clause adds distinct value with no redundancy.

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?

For a simple 3-parameter list-fetcher with full schema coverage and safety annotations, the description provides adequate context including pricing and auth. It omits explicit return format, but the absence of an output schema lowers the expectation, and the tool's purpose is straightforward.

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 100%, so the schema documents all three parameters thoroughly. The description adds only general mention of 'by real-estate category' and 'apartment listings', which does not enhance parameter understanding beyond the 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?

Description opens with a specific verb 'Pull' and names the exact resource 'live apartment listings straight from Tap.az', clearly differentiating it from sibling real-estate tools like emlakjet-istanbul or krisha-kz by marketplace and geography. The phrase 'Azerbaijan's biggest classifieds marketplace' anchors the tool's domain.

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 context is implied by naming Tap.az and Azerbaijan, but no explicit alternatives or when-to-use guidance are given. The only usage caveat is in the schema description noting that 'menziller' is the only verified category, which is not highlighted in the main description.

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