getSitesGatewaysSimCardUsed

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them — no indication of what SIM data is returned, whether the gateway must be online, or any failure behavior. With annotations present, the bar is lower, but this adds zero extra context.

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 short sentence with no wasted words, but it is so terse that nothing is front-loaded beyond the bare purpose. Efficient though under-informative.

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 simple read-only two-parameter tool with full schema coverage and no output schema, the description is minimally adequate. It doesn't clarify what the SIM card result contains, which would help an agent decide whether to call it, but complexity is low enough that this is acceptable.

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 100%, and both parameters (siteId and gatewayMac) are fully documented with patterns and discovery hints (listSites, listDevices) in the schema itself. The description adds no meaning beyond that, so the baseline 3 applies.

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 specific verb and resource: retrieves the SIM card information used by a gateway. An agent can distinguish this from siblings like getGatewayDetail or getGatewayWanStatus, though it doesn't explicitly say how it differs from those broader gateway tools.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of alternatives. It doesn't explain when to prefer this over getGatewayDetail or other gateway queries.

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