asset.pack_resources

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

Annotations carry no hints (readOnly, openWorld, idempotent, destructive all false), leaving the description as the sole source of behavioral disclosure. The description only mentions 'Risk: standard; maturity: L3' and that 'Per-request argument checks and session policy still apply', which are generic operational constraints rather than tool-specific behavior. It does not state whether the tool modifies state, reads data, or has side effects, so behavioral transparency is severely lacking.

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 extremely brief, which might suggest conciseness, but it is under-specified to the point of uselessness. It contains no information that helps an agent decide to use the tool, so it is not effective conciseness; it is omission.

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 tool's specific nature (a Blender harness command) and the absence of annotations, the description is wholly inadequate. It does not explain what 'pack_resources' does, what inputs are meaningful, or what the output schema represents. An agent has no basis to call this tool correctly.

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 75% (3 of 4 parameters documented), so the baseline is moderate. The description adds no parameter explanations beyond what the schema provides, and critically it does not clarify the undocumented '_expectedSceneRevision' parameter. Thus the description fails to compensate for the schema's gaps and adds no value to parameter understanding.

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 merely restates the tool name as a command ('PartMe Blender Harness command `asset.pack_resources`') without any explanation of what the command does. It fails to specify a verb, resource, or effect, leaving the agent to infer from the name alone. This is a tautology, not a purpose statement.

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 guidance is provided about when to use this tool versus any of the many sibling tools. There is no mention of context, prerequisites, or alternatives, so an agent cannot determine appropriate invocation conditions.

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