ztna_groups

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

The "[READ]" tag simply restates readOnlyHint=true, earning no credit. The one real signal, "opaque provider cursor", hints that results are paged by an opaque token, but it never explains that page_offset is the cursor field, that empty means first page, or what the response looks like. No annotation contradiction, since the read framing matches readOnlyHint.

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?

One sentence with no filler, so it is certainly concise, but concision here comes at the cost of under-specification. The bracketed tag occupies space without adding information beyond annotations.

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?

With no output schema, one required parameter, and a zero-coverage schema, the description carries nearly all the burden and delivers almost none of it. An agent still does not know what a group is here, what paging contract applies, or what fields come back.

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 4 parameters, so the description must compensate and does not. The required provider_id is never mentioned, and the "opaque provider cursor" phrasing awkwardly maps to a field named page_offset with no explanation of format or of limit/filter_text behavior.

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 verb and resource ("Search groups") and tags it as a read operation, but leaves "groups" ambiguous in a sibling set containing ztna_group, ztna_dns_groups, ztna_group_users, and ztna_collections. It never says whether these are identity-provider groups, DNS groups, or policy groups, so the agent cannot pick it confidently over ztna_group.

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 when-to-use, when-not-to-use, or alternative routing. The description does not tell the agent whether to use ztna_groups for listing versus ztna_group for a single lookup, nor when to use filter_text versus paging through everything.

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