view.present

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the 'Risk: read' is redundant. However, the description adds a useful prerequisite: 'Foreground window with a VIEW_3D area' which is a behavioral constraint. It does not contradict annotations, but it doesn't describe the actual operation or any side effects.

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 very short, which is good, but the first sentence repeats the tool name, and the risk/maturity information is partly redundant with annotations. The requirement sentence is useful, but overall the content is minimal and not front-loaded with the purpose.

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?

Despite having annotations and an output schema, the description fails to explain what the tool does. An agent cannot infer the purpose of 'view.present' from the given text. This is a critical gap for a tool with no domain parameters.

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%, so the schema documents most parameters. The description adds nothing about parameter semantics; it only mentions requirements. Since coverage is high, baseline is 3, but no additional value is provided.

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 only restates the command name and provides metadata (risk, maturity) without stating what action the tool performs. 'view.present' is ambiguous; it doesn't say what it presents or how. This is essentially a tautology of the name.

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 other view-related tools like blender_view_focus or blender_view_set. No alternatives or conditions are mentioned.

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