grease_pencil.add_material

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

Annotations are all false (readOnly, openWorld, idempotent, destructive), providing little safety context. The description carries the burden but only says 'Risk: standard; maturity: L3', which is generic and does not describe side effects, what gets mutated, or how the operation behaves. No contradiction exists, but the description adds almost no behavioral signal.

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 short (three sentences), but the first sentence merely repeats the title, and the other two provide generic metadata. Every sentence should earn its place, and these do not: they could be removed without losing useful information. This is under-specification, not effective conciseness.

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 an operation with 8 parameters, a non-default destination, and transactional requirements, the description is incomplete. The output schema exists, but the description still doesn't tell the agent enough to safely invoke the tool (e.g., how to choose the material, what `color` means in context). It provides no context that helps the agent understand when or how to use it.

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 moderate (50%), and the description does nothing to clarify the meaning of any parameter (e.g., `material`, `color`, `name`, `objectId`). The endurance on `_transactionId` and `_authorization` is untouched. The description adds zero parameter semantics beyond the sparse schema, so it fails to compensate for the coverage gap.

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 restates the command name ('PartMe Blender Harness command `grease_pencil.add_material`') and adds only generic risk/maturity metadata. It does not say what the command does (e.g., add a material to a grease pencil), so it's a tautology with no functional explanation.

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, what problem it solves, or how it differs from sibling tools like blender_grease_pencil_add_stroke or blender_material_attach_image_texture. The 'Per-request argument checks and session policy' line is procedural boilerplate, not usage guidance.

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