zcell_list_iccid_violations

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

Annotations already declare readOnlyHint=true; the description confirms read-only status. It adds minimal extra transparency (e.g., lookback window, return fields) but does not disclose pagination, rate limits, or other behavioral traits beyond what annotations cover.

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 concise with three sentences, front-loading the main action. Every sentence adds value with no redundancy.

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?

Given no output schema, the description should detail the return structure more explicitly. It mentions returned fields but omits query parameter usage. Completeness is adequate for a simple tool but lacks detail on outputs and optional parameters.

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?

The description explains 'days' as a lookback window but does not define iccid or policy_id beyond their names. With schema description coverage at 25%, the description only partially compensates; query parameter is not mentioned at all.

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 clearly states 'List the anomaly-policy violation events for one ICCID,' specifying the resource, scope, and returned fields (event type, zone, timestamp). It distinguishes from sibling tool zcell_list_anomaly_policy_violations by focusing on a single ICCID.

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?

The description implies usage for one ICCID but does not explicitly guide when to use this tool versus alternatives like zcell_list_anomaly_policy_violations. No when-not-to-use or alternative suggestions are provided.

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