zcell_get_sim_location_group

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

The description states 'Read-only' matching the readOnlyHint annotation and goes further by explaining the extra data returned, providing transparency beyond the annotation.

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, two sentences, with no redundant information, and gets straight to the point.

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?

It sufficiently explains what the tool does and what it returns (geo-fence, policies, membership buckets) without an output schema. It could be slightly more detailed but is adequate for a get operation.

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 only parameter group_id is present in the schema but the description does not elaborate on its meaning or format. Since schema coverage is 100%, baseline is 3, and no additional meaning is added.

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 the tool gets one SIM location group and distinguishes it from the list variant by adding detailed fields like geo-fence definition, anomaly policies, and ICCID membership buckets.

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 when to use this tool (when detailed info beyond summary is needed) and indicates it is read-only. It does not explicitly mention alternatives but the context is clear.

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