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

The description states 'Read-only' which aligns with the readOnlyHint annotation. It also adds the return type ('array of seller entities'), providing value beyond annotations. No contradictions found.

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 concise (3 sentences) and front-loaded with the core purpose. Every sentence adds value: the first states what it does, the second explains when to use it, the third clarifies idempotency and return type.

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 the high parameter count and no output schema, the description is incomplete. It lacks guidance on optional parameters like includeLogs, sellersFilter, pagination, and ordering. The agent would struggle to use this tool correctly without additional inference.

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?

With only 9% schema description coverage and 11 parameters, the description adds no parameter-level explanations. The address parameter is implied but not detailed. The configId parameter is described in the schema but not in the description. This is insufficient for an agent to select the correct parameters.

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 reads seller entities for a specific Ethereum address and explicitly distinguishes its use case: checking if a signerAddress exists before calling create_seller. This contrasts with sibling tools like create_seller, update_seller, or get_sellers.

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 provides a specific usage scenario (before create_seller) and implies a context (checking existence). However, it does not explicitly state when not to use this tool or mention alternatives like get_sellers, though the sibling list includes that.

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