Sellers get

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

Annotations already declare readOnlyHint and idempotentHint, so the description correctly does not repeat safety. It adds behavioral detail about the stale: true flag when trust metrics are older than 36 hours, which is useful context beyond annotations. No contradictions with annotations.

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 a single, efficient sentence that front-loads the primary purpose and then adds the trust signal detail and staleness behavior. No wasted words.

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 simple one-parameter read-only tool with no output schema, the description covers the return content (profile + trust signals) and a notable edge case (stale flag). It is adequate for an agent to call correctly, though it could mention exact output structure if needed.

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 already describes the sole parameter seller_id with a clear description ('UUID of the seller whose public profile to fetch'). Schema description coverage is 100%, so the description adds no additional meaning about the parameter. Baseline of 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?

The description clearly states the tool fetches a seller's public profile plus trust signals, with specific verb and resource. It distinguishes from siblings like seller_get_me (which likely fetches own profile) by implying it's for any seller by ID, and the mention of trust signals adds specificity.

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 does not explicitly state when to use this tool vs alternatives such as seller_get_me. It implies it fetches any seller's public profile, but there is no guidance on when to choose this over other seller-related tools. The presence of seller_get_me suggests a distinction, but it's not articulated.

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