ai_cloud_pull

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects (e.g., mirror_delete deletes local files) or permissions needed. The description only says 'download assets' without any behavioral context.

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 very short but not effectively concise; it is disjointed and contradictory (deprecated yet suggests using cloud API). It fails to front-load key information and wastes space on a confusing recommendation.

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?

With 6 parameters, no output schema, and no annotations, the description is grossly inadequate. It lacks essential context about behavior, return values, and usage scenarios, making it nearly unusable for proper agent 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 50%, but the tool description adds no additional meaning beyond what the schema provides. It does not explain or clarify any of the 6 parameters, leaving the agent without semantic guidance.

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 states 'DEPRECATED' and 'Descarga assets' but then says to use the cloud API directly, creating confusion about the tool's actual function. It is tautological and misleading rather than clearly stating what the tool does.

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 explicitly says 'DEPRECATED' and suggests using the cloud API directly, which is a clear alternative. This provides guidance on when not to use the tool and what to use instead, though it lacks details on specific scenarios.

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