render_region

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

The description discloses a critical behavioral fact beyond what annotations convey: the tool is not implemented. It also steers the agent to a working alternative. The destructiveHint=true annotation is not contradicted, and the stub status is enough to prevent an agent from actually calling it.

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 warning is front-loaded and the alternative is stated in a single clear sentence. The Args block is minimal and scannable; there is no filler or redundant repetition of the schema.

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 stub, the essential context is present: don't call this tool, use render_project, and get region bounds via get_regions. It is sufficient to prevent misuse, though a functional version would need region_index semantics and return-value documentation.

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%, so the description carries the full burden for explaining parameters. It documents output_path as 'Full path for output file' but never mentions region_index, leaving a required parameter completely unexplained.

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 does not actually state what render_region does; it only marks the tool as NOT IMPLEMENTED and points to render_project. This is a clear status signal, but the intended verb+resource behavior must be inferred from the tool name, so purpose clarity is only partial.

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?

It explicitly instructs the agent to use render_project instead and specifies how to obtain the needed data: 'with the region's start/end from get_regions.' This is direct, actionable routing guidance that resolves ambiguity with the sibling tool.

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