pro_visualize_named_camera

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's job is to add specifics, which it does: only MCP-owned cameras can be deleted, lens fields are readback-only, and no save occurs so export framing must be verified separately. These are meaningful operational caveats beyond the annotation flags, though the consequence of deletion (irreversibility) is not spelled out.

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?

Four short, dense sentences with the core capability front-loaded and constraints following. Nothing is redundant, though a slight restructure grouping action-scope notes together would read more cleanly.

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 destructive, non-idempotent mutation tool with seven undocumented parameters and no output schema, the description conveys the safety-critical constraints but omits the parameter contract, the meaning of 'apply' versus the other actions, and what an inspect call yields. Adequate as a warning label, incomplete as an operating manual.

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 0% across 7 parameters, so the description must carry the load and only partially does: it explains that position/target are absolute in millimetres and that lens fields are read-only, but says nothing about document_path, the MCP_ name pattern and default, roll_deg, activate, or which action values exist.

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 opens with a specific verb set and resource ('Inspect, create or update an owned native camera'), which tells an agent exactly what object is being manipulated. It distinguishes itself from the sibling pro_visualize_camera by emphasizing the 'named'/'owned MCP cameras' scope, though the mapping of 'create or update' onto the actual 'apply' action value is left implicit.

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?

'Can activate, deactivate or delete only owned MCP cameras' gives a strong usage boundary for the destructive actions, and 'verify actual Visualize export framing' implies a verification workflow. However, it never states when to pick this tool over the sibling pro_visualize_camera, nor when inspect vs apply is the right choice.

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