get_scene_visual_region_context

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a safe read, but there is no mention of permissions, whether results are paginated despite limit/cursor params, or what 'CAD facts' actually includes.

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 wasted words, but the brevity is achieved by omitting information the agent needs, making it under-specified rather than truly concise.

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?

An output schema exists so return shape needn't be explained, but with four undocumented parameters, no annotations, and no guidance on pagination or region identity, the description leaves significant gaps for a tool that requires two identifiers.

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?

All four parameters (manifest_path, region_id, limit, cursor) have 0% schema description coverage and the description adds no meaning for any of them — no format for manifest_path, no notion of what region_id refers to, no explanation of pagination semantics.

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?

States a specific verb and resource: read one visual region's CAD facts. The word 'one' implicitly distinguishes it from the listing siblings (list_visual_regions, list_scene_visual_regions), though no sibling is named directly.

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?

The phrase 'without sending all drawing nodes' hints at the efficiency rationale for using this over a bulk scene fetch, but it never says when to prefer it over list_scene_visual_regions or get_cad_scene_node, nor what prerequisites exist.

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