presentation-set-rendering

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/non-destructive profile is covered and the description does not contradict it. But the description adds nothing beyond that: it does not say whether unspecified fields are preserved or cleared, whether 'parameter' replaces the whole parameter set, or whether this only affects the final layout by default.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though its brevity borders on under-specification rather than true economy of information.

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 10-parameter mutation tool with no output schema and a crowded presentation-related sibling set, the description omits update semantics (merge vs replace), layout-scope behavior, and any routing guidance. The rich schema covers inputs, but the description leaves meaningful gaps an agent must guess at.

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 100% across all 10 parameters, including the id-vs-path rule, finalLayout default, and database prefix behavior, so the schema does the heavy lifting. The description adds no parameter meaning beyond the schema's own coverage, which is the baseline 3 case.

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 names a specific verb ('Updates') and resource ('a rendering placed on an item'), so the basic operation is unambiguous. However, it does nothing to distinguish itself from close siblings like presentation-add-rendering, presentation-switch-rendering, presentation-remove-rendering, or presentation-set-rendering-parameter, which an agent would need to choose between.

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 statement of when to use this tool versus its siblings (add / switch / remove / set-rendering-parameter), nor any prerequisite context such as needing the layout to exist first. The agent is left to infer usage entirely from the name.

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