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

Annotations already declare readOnlyHint=true,Skip and the description adds useful non-obvious context about the aggregation concept and ranking by member count. However,Skip it does not disclose the return shape,Skip pagination behavior,Skip or how q affects results,Skip so the behavioral picture is only partially filled in.

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 three tight sentences: concept,Skip concrete examples,Skip ranking behavior,Skip and a targeted use case. Every sentence earns its place and the most important framing is front-loaded.

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?

There is no output schema,Skip so the description must carry information about what the caller gets back,Skip but it never describes the result fields or list structure. It also leaves q,Skip page,Skip and limit semantics mostly implied rather than stated. For a 4-parameter tool with no output schema,Skip these are meaningful gaps.

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 only 25% and only the context parameter is documented in the schema. The description implies q relates to slugs ('two slugs look like separate vendors') but never explicitly explains q,Skip page,Skip or limit semantics. With such low schema coverage,Skip the description needed to compensate and did not.

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 defines an 'estate' as one company spread across multiple provider records)Skip and gives concrete examples (Amazon 237, Salesforce 27, Cisco 37). It states the tool browses these ranked by member count)Skip but it does not explicitly name or contrast sibling tools like get_estate or find_providers,Skip so it stops short of full sibling differentiation.

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 includes an explicit use case: 'Use this when two slugs look like separate vendors and you need to know whether they are one company.' This gives a clear when-to-use signal,Skip but it does not mention when not to use it or name alternatives,Skip leaving some guideline value on the table.

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