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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that auth is required, but does not disclose what the tool actually does upon invocation (e.g., creates a draft or live listing), side effects, validations, idempotency, or the return format. This is insufficient for a creation/mutation tool.

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 extremely concise with no wasted words, but it is under-specified to the point of being minimally useful. A single sentence does not provide the structure needed to guide an agent, though it is not verbose or poorly arranged.

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 tool's complexity (8 parameters, 4 required, enums, no output schema) and the absence of annotations, the description is severely incomplete. It lacks any explanation of required fields, expected behaviors, or what happens after creation, making it inadequate for correct invocation.

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 has 8 parameters with 0% schema description coverage, and the description mentions none of them. No parameter names, purposes, or constraints are explained, leaving the agent to rely solely on the bare schema types and enums without any semantics.

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 uses a specific verb ('List') and a clear resource ('a new app for sale'), which conveys the tool's purpose. However, it does not distinguish create_listing from siblings like publish_listing or deploy_listing, leaving ambiguity about whether this creates a draft or a live listing.

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 usage guidance beyond 'Requires auth' is provided. There is no mention of when to use this tool versus alternatives, nor any exclusions or prerequisites. The description gives no context for deciding between create_listing and publish_listing or other sibling tools.

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