get_cics_region_stats

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by noting fields are release-dependent ('your CMCI release provides'), which warns the agent not to assume a fixed field set. It says nothing about size of response, error behavior when the region is unknown, or CMCI connectivity requirements.

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 a useful parenthetical; no boilerplate, no repetition of the tool name, nothing that could be cut.

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 three-parameter read tool with no output schema, the description hints at return contents (uptime, task counts) but explicitly declines to pin them down, leaving the agent unable to predict the response shape. The more serious omission is disambiguation from get_cics_region_status, which is the main correctness risk here.

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 coverage is 100% and all three parameters carry inline descriptions (APPLID, CMCI context, named environment), so the schema does the heavy lifting. The description adds no meaning beyond the schema — it does not clarify how 'context' interacts with 'environment' or what happens when both are supplied.

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?

Names a specific resource and source (CICS region statistics from the CMCI CICSRegion resource) and enumerates representative fields (uptime, task counts). However, it does not distinguish itself from the near-identically named sibling get_cics_region_status, so an agent cannot tell from the description alone which to call.

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 statement of when to use this tool, when not to, or how it relates to get_cics_region_status, list_cics_regions, or list_environments. The only hint is the 'environment' parameter's parenthetical pointing at list_environments, which is schema text, not description guidance.

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