ztna_region

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

The readOnlyHint annotation already declares this a safe read operation, and the "[READ]" prefix merely repeats that. The description adds no behavioral context beyond the annotation: nothing on what happens when the region name is unknown, whether names are case-sensitive, or what the lookup matches against.

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 single sentence is front-loaded and wastes no words, but its brevity reflects under-specification rather than economy; the same length could have carried the region_name format it omits. Structure is clean, content is thin.

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?

This is a simple one-parameter read with no output schema, so a brief description can suffice, but the total absence of parameter guidance leaves the agent guessing at the input format. For a naming-based lookup tool, that is a real gap in calling it correctly.

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 sole parameter region_name is documented nowhere — neither the schema nor the description says whether it expects a display name, slug, or identifier. With a single required undisclosed parameter, the description needed to carry this meaning and does not.

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?

"[READ] Read one ZTNA region" gives a specific verb plus resource, and the word "one" signals single-item retrieval as opposed to the plural sibling ztna_regions. It stops short of naming ztna_regions as the list alternative, so the differentiation is implied rather than stated.

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 explicit when-to-use statement and no named alternative; the agent must infer from the singular/plural naming and the [READ] tag that this is the single-region fetcher. No prerequisites, error conditions, or guidance on choosing it over ztna_regions is provided.

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