marketplace

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

No annotations are provided, so the description carries the full burden. It discloses that 'install' adds a listing to a workspace (mutative). However, it does not mention authorization requirements, reversibility, or any side effects. For a tool with both read and write actions, more transparency is expected.

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 two sentences long, front-loading the core purpose and then detailing actions with clear syntax. Every sentence is informative, with no wasted words.

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 6 parameters, full schema coverage, and no output schema, the description provides a solid overview of how to use the tool. It explains the action sequence but does not hint at the return format of search or get results, which would enhance completeness slightly.

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%, but the description adds value by grouping parameters by action (e.g., 'slug (action=get or install)' and 'query (action=search)') and explaining the workflow. This clarifies parameter usage beyond the schema's individual descriptions.

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 clearly states the verb-resource: 'Browse, inspect, and install shared skills, agents, and MCP servers from the Contextium Marketplace.' It distinguishes from siblings by focusing on marketplace-specific actions (search, get, install) that no other sibling tool covers.

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 explicit instructions: 'Typically search first to find a slug, then get or install with it.' It also maps each action to its use case (search to browse, get for details, install to add). This gives clear when-to-use guidance.

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