marketplace_bundles

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'browse and manage' but the schema only allows list, get, and suggest actions, which are read/suggestion operations. The description doesn't disclose rate limits, side effects, or the read-only nature of actions, making 'manage' potentially misleading.

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 a single sentence with a parenthetical clarification, making it extremely concise and front-loaded. Every word earns its place, and it avoids repetition of schema details.

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 six parameters, one enum, and no output schema, the description is sparse. It fails to explain the purpose of list/get/suggest actions or how bundleId, category, curatedOnly, and userAddress interact with actions, leaving an agent without sufficient context for correct invocation.

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 100%, so all six parameters are already documented. The tool description adds no semantics about how actions relate to parameters or what 'suggest' does, so it stays at the baseline without adding value beyond the schema.

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 uses specific verbs ('browse and manage') and identifies the resource ('tool bundles'), with a clarifying parenthetical about pre-packaged combinations with discounts. It distinguishes from sibling marketplace tools by focusing on bundles, though 'manage' overstates the read/suggest actions supported.

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 provides no guidance on when to use this tool versus other marketplace tools, or how to choose between list/get/suggest actions. It implies a use case for bundles but doesn't exclude alternatives or state any prerequisites, leaving usage to be inferred.

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