ai_cloud_push

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic upload action without mentioning overwrite behavior, authentication needs, rate limits, or effects on existing data. This is insufficient for safe invocation.

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, no waste, front-loaded with the main action. Every word is necessary for conveying the core 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?

For a tool with 4 parameters, no output schema, and no annotations, the description omits key details: behavior for 'type=all', interaction between 'slug' and other params, and expected return values or errors. The presence of overlapping siblings (ai_cloud_sync) further highlights the need for more context.

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 description adds value for the 'type' parameter by listing the asset categories (skills, prompts, specs) that map to its enum values. However, it does not explain the 'slug', 'project_slug', or 'workspace' parameters beyond what the schema already provides. With 50% schema coverage, the description compensates partially but not fully.

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 action ('Publica' meaning publishes) and the resource (local assets to StandarCloud, specifically skills, prompts, and specs). Although sibling tools exist, the name and description distinguish it as the upload counterpart to ai_cloud_pull and ai_cloud_sync.

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 its siblings like ai_cloud_sync (which might handle bidirectional sync) or ai_cloud_status. It lacks context on prerequisites, exclusions, or typical use cases.

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