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

With no annotations, the description must carry the behavioral burden; it usefully enumerates the returned fields (name, price, image URL, affiliate link, ASIN, metadata), aiding the agent. But it omits rate limits, failure modes, and explicitly stating this is a non-mutating read—search implies read but is never asserted, and the platform-connection prerequisite only appears in the schema.

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?

Two compact sentences, front-loaded with the purpose and then the return shape and workflow handoff. Every sentence carries 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?

Given a 3-param tool with full schema coverage and an output schema, the description covers purpose, return contents, and downstream usage adequately. The only notable gap is the platform-integration prerequisite, which lives in the schema rather than the description.

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 fully documents query, platform (with supported values), and limit. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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 (Search) and resource (products) scoped to 'a connected affiliate platform', and clarifies it returns live catalog data rather than stored records, which implicitly separates it from siblings like get_product or list_store_products. It does not explicitly name any sibling, so it falls short of a 5.

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 line 'Results are ready to pass directly to auth.create_product' gives a clear workflow context (find then create), which tells the agent when to reach for this tool. However, there are no exclusions or explicit alternatives (e.g., when to use list_store_products instead), 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.