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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond that – no mention of auth needs, rate limits, error behavior when a seller_id is invalid, or data freshness. It essentially restates the return payload, which the output schema already defines.

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?

A single tight sentence with the resource front-loaded and zero filler. Appropriately sized for a one-parameter read tool, though its brevity reflects under-specification rather than disciplined editing.

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 values need no explanation, and the operation is a simple read-only lookup. However, with ten marketplace-related siblings, the description gives no help on where seller_id comes from or how this differs from listing-level tools, leaving a real gap for a shallow tool.

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?

Single parameter seller_id with 100% schema description coverage, so the schema carries the burden; baseline is 3. The description adds nothing about format (numeric ID vs. username) or where the ID is sourced.

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 (Get) and resource (seller profile) with the payload contents enumerated: ratings, reviews, badges. Clearly distinct from sibling tools like facebook_marketplace_listing, which fetches a listing rather than a seller. No explicit sibling differentiation in text, so not 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?

No indication of when to use this tool versus facebook_marketplace_listing, facebook_marketplace_search, or facebook_search_people. An agent must infer that seller_id comes from a listing/search result. No exclusions or prerequisites stated.

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