upload_theme

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

Discloses key behavior: packages directory, uploads, installs without activation, returns validation errors/warnings. However, no annotations exist, and it omits details like idempotency, overwrite behavior, required permissions, or rate limits.

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, front-loaded with the key disambiguation (not activating), no filler. Every sentence provides essential information.

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?

Tool has only one parameter, output schema exists, and description covers outcome and error handling. Missing overwrite behavior or theme ID return, but sufficient for an upload tool with clear purpose.

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?

With 100% schema coverage, the description adds minimal value beyond the schema by implying packaging of the directory. The schema already describes theme_path as 'Path to the theme directory to upload.'

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?

Description uses specific verb 'upload', resource 'theme', and explicitly states 'WITHOUT activating it', clearly distinguishing from sibling tools like activate_theme and create_theme.

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?

Clearly explains that the theme is installed but inactive, allowing manual review and activation, and mentions validation on upload. However, it does not explicitly differentiate from other upload tools like upload_image or create_theme.

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