Create Admin Maintenance Clean Temp

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

With no annotations, the description must disclose behavioral traits on its own. 'Clean Temp' implies some kind of cleanup but does not state whether data is deleted, whether the action is reversible, whether admin authorization is required, or what the output represents.

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 this is under-specification rather than effective conciseness. A two-word phrase does not provide enough information to justify its place as the only descriptive content for the tool.

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 an admin maintenance action with no annotations, the description is severely incomplete: it omits the operation's effect, scope, prerequisites, relationship to sibling cleanup tools, and return semantics. The simple input schema does not compensate for the lack of operational 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?

Schema description coverage is 0%, and the description says nothing about the accept-language parameter. The schema provides only a name and type, leaving the agent to guess whether this is a header/context parameter or a functional input.

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 'Clean Temp' is essentially a restatement of the tail of the tool name and gives only a vague verb-object fragment. It does not explain what 'Temp' refers to, what cleaning entails, or how this differs from sibling tools like create_admin_maintenance_clean_images or create_admin_maintenance_clean_recipe_folders.

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?

There is no guidance on when to use this tool, what conditions warrant it, or which alternative should be chosen. The sibling cleanup/maintenance tools are not referenced, so an agent cannot determine the correct context for this operation.

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