Fetch all SIM cards

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the trailing "Read-only" mostly repeats structured data; the endpoint path (GET /sim_cards) adds marginal tracing value. The description says nothing about pagination behavior or the caveat that per_page is not honored by every endpoint, which is genuinely useful behavioral context that only the schema hints at.

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?

Two short sentences, front-loaded with the action and scope. It is efficient almost to a fault — the "Read-only" clause duplicates annotations rather than earning its place, but nothing is bloated.

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 parameterized list endpoint with no output schema, the definition is minimally adequate: safety profile comes from annotations and parameters from the schema. It does not explain pagination semantics (how to iterate pages, what per_page limitation means in practice), which is the main gap for a paged listing tool.

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%, so all four parameters (page, per_page, filter_status, response_format) are already documented with bounds, defaults and enums. The description adds no parameter guidance of its own, 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?

The description uses a specific verb ("Fetch") and resource ("SIM cards") and the plural scope implies enumeration, which implicitly separates it from the singular sibling placetel_get_sim_card. However, it does not name or contrast with that sibling explicitly, leaving the distinction to inference from the tool name.

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 versus placetel_get_sim_card, nor any prerequisite or context guidance. A caller must infer from the name alone that this is the bulk-listing variant.

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