sellersprite_describe_operation

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

With no annotations, the description reveals that the tool returns detailed breakdown (purpose, request, response, etc.), indicating read-only behavior. It does not explicitly state idempotency but the listed output components imply no side effects.

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?

Single sentence that begins with the core purpose, listing key components efficiently. Could be slightly more structured but is clear and concise.

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 a single parameter and no output schema, the description adequately outlines what is returned. However, it omits that the operation should come from list_operations, which would help agent ensure validity.

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 only parameter 'operation' lacks schema description, and the tool description merely says 'one operation' without specifying format or source (e.g., from list_operations). The description adds minimal meaning beyond the schema field name.

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 explains one operation, listing components like purpose and request. It is reasonably distinct from sibling tools which list, call, or check session status, though explicit differentiation is missing.

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 implies use before calling an operation, but provides no explicit guidance on when to use vs alternatives or when not to use it. Missing context about prerequisites.

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