cloud.pushSkill

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 the upsert behavior ('Create or update') and the API key requirement, but fails to mention error states, whether updates overwrite or merge, rate limits, or idempotency. This is insufficient for a mutation tool.

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 concise at two sentences, with the first sentence stating the purpose and the second noting an important requirement. No unnecessary words, though the parameter information is missing.

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 no output schema, no annotations, and 3 parameters with zero description coverage, the description is too sparse. It does not explain return values, error handling, or the distinction between creation and update, leaving the agent underinformed.

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?

The input schema has 3 parameters (slug, title, body_md) with 0% schema description coverage. The description adds no information about these parameters beyond what is already in the schema definition.

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 'Create or update a skill in the cloud library.' It uses a specific verb (create/update) and resource (skill in cloud library), and distinguishes from sibling tools like cloud.listSkills (list) and cloud.pullSkill (download).

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 mentions the requirement of MODELBOUND_API_KEY, implying authentication context. However, it does not explicitly state when to use this tool versus siblings like cloud.installMarketplaceSkill or cloud.pullSkill, nor does it provide when-not-to-use guidance.

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