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

Annotations already declare this a safe, idempotent, non-destructive read. The description adds genuinely non-derivable context: it is a paid x402 call with a specific price ID, it returns explainable match evidence, and it will not silently choose among ambiguous candidates. It stops short of saying how the payment is settled or what form the returned evidence takes.

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?

Four short clauses, each earning its place: payment model first, then what is matched, then the key behavioral guarantee, then the price ID. No filler and nothing buried.

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 no output schema and a nested-object input, the description does enough: it names the entity domains in scope implicitly, discloses the paid nature and price ID, and characterizes the return ('explainable match evidence') and the ambiguity policy. The main gap is the interaction with sibling lookup tools and the input-shape requirement, both of which the agent must find in the 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 coverage is 67%, including a documented entity_type enum and an anyOf requirement, so the schema carries most of the burden. The description adds nothing about entity_type, identifiers, or the 'at least one of identifiers/attributes' rule, so it neither compensates for the gap nor adds meaning 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?

States a specific verb and scope: matching incomplete or conflicting supplier/location/organization attributes to trusted master-data candidates, with the no-silent-choice guarantee. It is distinguishable from get_master_data_golden_record and search_master_data by implication, but no sibling is named, so the differentiation is not explicit.

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?

"Incomplete or conflicting" implies the triggering condition, so usage is inferable. However, the description never says when to prefer search_master_data or get_master_data_golden_record instead, nor does it surface the domain exclusions (customer/asset/person, reference data) that the schema carries — an agent would have to open the schema to learn them.

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