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 explicitly states that calling the tool 'writes nothing' and returns a structured 'not available' response, which accurately communicates that the tool is a safe no-op stub. This is exemplary transparency for a disabled endpoint.

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 with no filler. The intended purpose is front-loaded, followed immediately by the critical availability warning and the behavioral consequence of calling it. Every sentence earns its place.

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?

For a tool that always returns 'not available' and writes nothing, the description is complete. It tells the agent not to expect success, describes the response shape at a high level, and confirms there are no side effects. Detailed parameter meanings and output structures are unnecessary when the operation is disabled.

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 five parameters with 0% description coverage, and the description does not explain any of them. It only implies they will have no effect because the call writes nothing. For an unavailable stub this is acceptable in practice, but the description still adds no semantic meaning to the individual 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 states a specific verb and resource: submit a new skill listing for sale. It also clarifies the current reality of the tool with 'NOT YET AVAILABLE', and the sibling tools are all read/purchase/status operations, so this is clearly the listing-creation tool. It is unambiguous and distinguishable.

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 explicitly tells the agent the tool is not yet available, meaning it should not be used to actually list a skill. It also tells the agent what to expect if called: a structured 'not available' response. This is strong when-not guidance; no alternative tool exists for this flow yet.

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