create_admin_maintenance_clean_temp

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

No annotations are provided, placing the full burden on the description. The description is a mere two words, disclosing nothing about behavioral traits such as what gets destroyed, authentication needs, rate limits, or side effects. For a maintenance tool that likely performs destructive operations, this is critically insufficient.

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?

While extremely concise, the description is under-specified to the point of being unhelpful. Every sentence should earn its place, but 'Clean Temp' is not a sentence; it lacks structure and essential context.

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 the complexity of the tool (destructive maintenance operation, many siblings, optional parameter, no annotations), the description is completely inadequate. It does not explain the scope of 'temp', the return value (output schema exists), or any prerequisites. The tool's role in the maintenance workflow is entirely opaque.

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 does not mention the single optional parameter 'accept-language'. The description adds no meaning beyond the schema, failing to explain how or why the parameter might be used.

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 only slightly more informative than the tool name, essentially a tautology. It does not specify what 'temp' refers to or provide a clear verb-noun relationship. While it hints at cleaning temporary data, it's too vague to distinguish it from sibling tools like 'clean_images' or '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?

No usage guidelines are provided. There is no indication of when to use this tool versus alternatives like 'create_admin_maintenance_clean_images' or 'create_admin_maintenance_clean_recipe_folders'. The description offers no context or prerequisites.

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