render.configure

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the operation is a mutation and not idempotent. The description adds 'Risk: standard; maturity: L3' and mentions argument checks and session policy, which provides a little operational context but does not disclose what side effects occur (e.g., changes render settings, requires authorization, transaction handling). With minimal annotation coverage, the description fails to carry the burden of behavioral disclosure.

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 text is very short, but that brevity is due to under-specification rather than conciseness. It does not front-load key information like what the command does or what parameters matter. It spends characters on risk/maturity labels that are not immediately actionable for the agent.

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 complex tool with 13 parameters, an output schema, and low schema coverage, the description is severely inadequate. It fails to explain the purpose, parameter semantics, prerequisites, or return behavior. An agent cannot determine how to correctly invoke this tool without additional 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 only 31%, meaning most of the 13 parameters (engine, width, height, samples, etc.) are undocumented in both the schema and the description. The description does not mention any parameter, its meaning, defaults, or relationships. It entirely fails to compensate for the low schema coverage.

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 identifies the tool as 'PartMe Blender Harness command render.configure' and provides risk/maturity labels. It does not state what the tool actually does (configuring render settings) nor distinguish it from siblings like blender_render_configure_passes or blender_render_inspect. This is a tautology that restates the name/title without conveying purpose.

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 given on when to use this tool versus alternatives. It mentions 'Per-request argument checks and session policy still apply' but that is a generic requirement, not usage context. There is no indication of scenarios, prerequisites, or when not to use it.

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