update_marketplace_listing

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

The description implies a mutation operation ('update') but does not disclose any behavioral traits beyond what is obvious. With no annotations, it fails to clarify whether updates are partial/merge or full replacement, error conditions, or idempotency. A score of 3 is given because it minimally conveys the operation type.

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 (one short sentence), which is positive for brevity but lacks structure. For a tool with 12 parameters, a single sentence is insufficient to convey essential information.

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 (12 parameters, no schema descriptions, no output schema, no annotations), the description is vastly incomplete. It fails to explain required fields, update behavior, or any important context.

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%, and the description (just 'Update a marketplace listing') adds no meaning to any of the 12 parameters. It does not hint at which parameters are required or how they affect the update. This is insufficient.

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 'Update a marketplace listing' clearly identifies the verb (update) and resource (marketplace listing). It distinguishes from sibling tools like create, delete, and get for listings. However, it does not specify the scope of updates (e.g., which fields can be updated).

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 provided on when to use this tool versus alternatives like create_marketplace_listing or delete_marketplace_listing. It lacks instructions on prerequisites (e.g., the listing must exist) or when not to use it.

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