render_region

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

No annotations are provided, and the description discloses the critical behavioral trait that the tool is not implemented, preventing wasted calls. It doesn't elaborate on the error response, but the key limitation is stated.

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 extremely concise: the most important information ('NOT IMPLEMENTED') is front-loaded, and every sentence serves a purpose. No filler.

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 non-implemented tool with no output schema, the description provides enough context: it declares unavailability and points to an alternative. The only gap is the lack of detail on region_index, but that is less critical given the tool's status.

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?

With 0% schema description coverage, the description must compensate. It describes output_path ('Full path for output file') but does not define region_index. The redirect to get_regions implies region_index relates to regions but does not state its format or meaning explicitly.

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 states 'NOT IMPLEMENTED' and redirects to render_project. While it doesn't explicitly say 'renders a region', the name plus the redirect make the tool's (non-)purpose clear. It distinguishes itself from siblings by naming render_project as the alternative.

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 says not to use this tool and instead use render_project with the region's start/end from get_regions. This gives clear when-not-to-use and how-to-get-parameters guidance.

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