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

With no annotations, the description carries the behavioral disclosure burden; it discloses that the call is synthetic, sandbox-only, and involves no payment or live provider call. It stops short of explaining 'bounded' or failure behavior, but for a read-only sandbox retrieval this is meaningful transparency.

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 short and front-loaded, but it repeats the required-field list and the 'seller public profile' concept. The parenthetical '(schema_version, data_mode, fixture_id, and the capability id field(s))' is redundant after the required-fields sentence and adds confusion rather than clarity.

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?

An output schema exists, so return-value documentation is not required. The description covers purpose, sandbox context, and required request fields, but the ambiguous 'capability id field(s)' and the lack of any guidance on how to populate values leave an agent needing to infer request construction.

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?

The input schema is an opaque 'request' object with additionalProperties: true and no inner property descriptions (0% schema coverage), so the description must compensate. It lists the required fields (schema_version, data_mode, fixture_id, seller_id) but the later phrasing 'the capability id field(s)' is ambiguous and no value formats or allowed values are given.

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 the resource name and uses a specific verb ('retrieve') plus a clear scope: 'bounded synthetic public profile for a single seller id.' It also flags 'Sandbox-only, no live provider call, no real payment,' which separates it from the live/discover siblings. This is enough for an agent to know what it does.

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?

It explicitly states when this tool applies ('Sandbox-only') and what it does not do ('no live provider call, no real payment'). It does not name a specific sibling alternative such as discover_seller_public_profile_v0, so the routing guidance is clear but not exhaustive.

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