manage_module_archive

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

No annotations are provided, so the description carries the full burden of behavioral transparency. It explains the toggle behavior (True=archive, False=unarchive) but does not disclose side effects, permission requirements, reversibility, or response format. For a mutation tool, this is a notable gap.

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 exceptionally concise and front-loaded. The first line states the action, and the arg list is clear and minimal. Every sentence contributes without any fluff or repetition.

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 simple toggle tool, the description covers the purpose and all parameters. However, with no output schema and no annotations, it omits any mention of return values, error conditions, or side effects. It is adequate but not fully complete for a mutation operation.

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%, so the description is the only source of parameter meaning. All three parameters are mentioned, with the archive parameter clearly defined as 'True to archive, False to unarchive.' However, project_id and module_id are only described as 'UUID of the project/module,' which adds little beyond the property names.

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 opens with a specific verb and resource: 'Archive or unarchive a module.' This clearly states the tool's action and object, and distinguishes it from sibling tools like manage_project_archive, manage_cycle_archive, and manage_work_item_archive which target different resources.

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?

Usage is implied by the resource type (module), but there is no explicit guidance about when to use this tool versus alternatives like manage_project_archive or manage_cycle_archive. No preconditions or exclusions are mentioned, so the context is clear but not fully elaborated.

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