resave_packages

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

No annotations are provided, and the description only says 'resave' and names the commandlet. It does not disclose that this overwrites package files, may be a heavy operation, or that it affects all assets, which is important for a bulk mutation tool.

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?

One sentence, front-loaded with the verb and scope, and includes the commandlet detail without any filler. Deserves full marks for efficiency.

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?

The tool is simple with one optional parameter and no output schema, and the description is adequate for basic understanding. However, as a bulk mutation operation it would benefit from a warning about destructive side effects or a note about expected runtime, so completeness is only partially addressed.

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?

The description does not mention the optional 'directory' parameter, but the input schema fully documents it with 'Limit to a specific content directory', so schema coverage is 100% and no additional description is required.

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 a specific verb ('Bulk resave'), a clear scope ('all packages in the project'), and the underlying commandlet ('ResavePackages'), making it easily distinguishable from sibling save/asset utilities.

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 phrase 'all packages in the project' implies a project-wide resave workflow, but the description gives no explicit when-to-use context, exclusions, or alternatives such as save_all or save_asset.

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