add_marketplace

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

No annotations are provided, so the description carries full burden. It discloses authentication requirements and supported providers, but fails to mention side effects (e.g., overwrites existing repo configurations?), required permissions, rate limits, or error states. The 'register' action's behavioral details are insufficient.

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, front-loaded with the primary action and followed by context. Every sentence adds value without redundancy. Perfectly concise for the purpose.

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 complexity (7 parameters, mutation, no annotations) and existence of an output schema, the description is too brief. It does not explain the registration process, return values, error conditions, or prerequisites. For a registration tool, missing parameter details severely limits completeness.

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%, meaning no parameter descriptions in the schema. The description adds almost no semantic value for the 7 parameters. It mentions 'per-repo authentication' but does not explain token_env, branch, author_name, author_email, or enabled. This leaves the agent without necessary parameter context.

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 tool registers a plugin marketplace repository, distinguishing it from siblings like publish_to_marketplace and remove_marketplace. It specifies supported providers (GitHub, GitLab, Bitbucket) and mentions per-repo authentication, making the purpose specific and actionable.

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 implies this tool is used before publishing skills, but does not explicitly say when to use vs alternatives like publish_to_marketplace or install_skill. There is no mention of prerequisites or conditions where this tool should not be used.

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