get_agent_marketplace_listing

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

With no annotations, the description carries the behavioral burden. It communicates that this is a read operation and adds 'persisted' and 'immutable revision' context. It does not address auth requirements, not-found behavior, or the effect of include_inputs, but for a single-object getter the provided level is minimally adequate.

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?

One sentence containing the core purpose with no filler or repetition. It is front-loaded and easy to parse, though it is arguably too terse to carry the full semantic load.

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?

Despite having an output schema, the description omits the meaning of 'listing' in the agent marketplace, what a revision is, and what include_inputs controls. Coupled with no usage guidance, an agent is left to infer important decision context from the tool name and parameter titles alone.

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 0%, so the description must compensate. It loosely maps listing_id and revision_id ('persisted UUID listing', 'immutable UUID revision'), but it does not explain include_inputs, revision semantics, or valid identifier formats. The description adds little beyond the parameter names.

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 names a specific resource ('persisted UUID listing') and a specific action ('get one'), which distinguishes it from list_agent_marketplace_listings and search_agent_marketplace. However, 'persisted UUID listing' is terse jargon and does not clarify the marketplace domain beyond the tool name.

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 guidance is given on when to retrieve a listing by ID rather than using list_agent_marketplace_listings or search_agent_marketplace, nor when the optional revision_id should be supplied. The implied usage is ID-based retrieval, but alternatives and exclusions are never stated.

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