marketplace_list_applications

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a genuinely useful behavioral trait beyond those: 'Secret fields are redacted', telling the agent that returned data is partially masked. It does not discuss pagination or result size, so it falls short of 5.

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?

Two sentences, front-loaded with the action and scope, followed by the returned fields and the redaction caveat. No filler or redundancy; every phrase 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?

No output schema exists, and the description compensates by enumerating the main returned fields and noting redaction. It omits pagination/result-size behavior, but for a straightforward read-only list tool this is a minor gap.

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 coverage is 0% and the single parameter partner_id is never named, so the schema does not compensate. The phrase 'in a developer account' implicitly scopes the query to an account identifier, partially mapping to partner_id, but no type, format, or meaning is added explicitly.

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 ('List applications in a developer account') and enumerates what each item contains (card configuration, permissions, system-user ID, short links, moderation state). The plural 'list' distinguishes it from the singular marketplace_get_application, but no sibling is named explicitly.

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 scope 'in a developer account' implies when to use it (enumerating apps for an account), but there is no explicit when-to-use vs when-not, no mention of the alternative single-app retrieval (marketplace_get_application), and no prerequisites stated.

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