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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing the ranking order (by member count), the pricing tier (B1, single-entity synthesis, $0.01/call, included in Understanding and Influence) and a pointer to apis://prices — real operational context an agent can act on.

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?

Front-loads the definition of an estate, then the routing cue, then ranking and pricing. Every clause is relevant, though the pricing sentence is dense and could be tightened; the 'UNDERSTANDING —' label adds mild clutter.

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 read-only, four-parameter search tool with no output schema, the description supplies the concept, the ranking semantics, and cost. It does not describe the shape of an estate record (members, slugs), a minor gap given there is no output schema to lean on.

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% with four well-documented parameters, so the schema carries the semantic load. The description adds nothing about q, page, limit, or context, which is acceptable at this coverage level but earns only the baseline.

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?

States a specific verb+resource (browse corporate estates) and defines the non-obvious domain concept: one company whose API surface spans many provider records, with concrete examples (Amazon 237, Salesforce 27). The ranking rule (by member count) further pins down what the tool returns, so an agent can distinguish it from provider-level tools like find_providers.

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?

Gives a concrete triggering condition: 'Use this when two slugs look like separate vendors and you need to know whether they are one company.' That is a clear when-to-use signal, but it names no alternative tool or exclusion, so it stops short of full routing guidance.

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