object.rename

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

All annotations are false (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), so the description carries full responsibility for behavioral disclosure. It provides none beyond vague 'Risk: standard' and 'maturity: L3', which are internal metadata. It does not state side effects, idempotency, or required permissions.

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 short but not concise in a meaningful way—it omits essential information. It is front-loaded with the command name but provides no functional detail, making it under-specification rather than efficient writing.

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 7-parameter mutation tool with low schema coverage and no description of behavior or return values, the description is grossly inadequate. The agent cannot correctly call this tool without external knowledge.

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 43%, leaving 4 of 7 parameters (name, newName, objectId, _expectedSceneRevision) undocumented. The description adds zero parameter guidance, so the agent cannot infer how to specify the target object or the new name.

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 is a tautology: it merely restates the tool name ('PartMe Blender Harness command `object.rename`') without stating the verb, resource, or effect. It does not explain that the tool renames a Blender object, nor does it distinguish it from siblings like blender_object_delete or blender_object_duplicate.

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 versus alternatives. It does not mention conditions, prerequisites, or exclusions. The phrase 'Requirements: Per-request argument checks and session policy still apply' is generic policy boilerplate, not usage direction.

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