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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' adds no new behavioral insight. There is no mention of rate limits, data freshness, pagination limits, or any side effects. Beyond the safety hint, the description contributes little behavioral context.

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 two sentences, front-loaded with the main action, and every word adds value. It efficiently communicates purpose, optionality, and output format without 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 10 parameters (1 required, no output schema), the description is insufficient. It does not explain pagination (sellersSkip, sellersFirst), filtering (sellersFilter), ordering (sellersOrderBy, sellersOrderDirection), or the structure of included entities. For a complex query tool, more detail is 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?

Schema description coverage is only 10%, with only configId having a full description. The description vaguely mentions 'Optionally includes related offers, exchanges, funds, and logs' but does not elaborate on the meaning of parameters like includeLogs, sellersSkip, sellersFilter, or sellersOrderBy. It fails to compensate for the low schema coverage.

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 it reads seller account entities from the Boson subgraph, optionally including related data. It distinguishes itself from sibling tools like get_sellers_by_address (which filters by address) and update_seller (which writes). The verb 'Reads' and resource 'seller account entities' are specific.

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 versus alternatives. It mentions optional includes but lacks guidance on when to choose get_sellers over get_sellers_by_address or other read tools. No exclusion criteria or context for selection is provided.

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