ruddur_list_my_marketplace_listings

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful context about the required OAuth scope (marketplace.read or marketplace.manage) and the ownership filter (owned by the creator), going beyond the structured annotations without contradicting them.

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?

A single, front-loaded sentence that states the core purpose and auth requirement. No filler or redundant information – every word 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?

The tool has no output schema, and the description gives no hints about pagination, filtering, or return structure. While annotations cover safety well, the unresolved body/query parameter semantics and lack of usage detail leave gaps for a list operation.

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 schema descriptions are generic boilerplate: 'body' describes POST/PUT/PATCH operations, which is misleading for a list operation, and 'query' offers no specifics. The description itself does not clarify what body/query mean for this tool. The agent receives no actionable parameter 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?

Clearly states the tool lists marketplace listings owned by the creator, using a specific verb and resource. This distinguishes it from sibling tools like create/update/delete marketplace listings and other list tools.

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 on when to use this tool versus alternatives. The only added information is an authorization scope requirement, not usage context. It does not mention when to prefer this over other listing tools or how it differs from search-like tools.

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