getSuppressions

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses that the operation is read-only, uses GET, and has a rate limit of 100 requests per minute. However, it does not disclose pagination behavior, default values, possible errors, or what the response contains.

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 compact and front-loaded: the core purpose appears first, followed by essential rate-limit and read-only information. There is no redundant filler; every phrase contributes operational value.

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 annotations, no output schema, and 0% parameter coverage, the description is too sparse to be complete. It covers the basic operation and rate limit, but lacks parameter semantics, pagination/defaults, and return-shape expectations, which an agent would need to call the tool accurately.

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 0%, and none of the three parameters (type, limit, offset) are explained in the description. It does not clarify what 'type' values are valid or how limit and offset behave, leaving the agent without enough information to invoke the tool correctly.

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 the specific verb 'List' with the resource 'suppressions' and confirms the operation with 'GET /postframe/suppressions'. It clearly identifies what the tool does, though it does not explicitly differentiate among the many sibling get/list tools beyond the resource 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?

The description provides operational context such as 'rate limit: 100 requests per 1m' and 'Read-only', but it gives no guidance about when to use this tool versus alternatives like listCoupons, getEmails, or other list endpoints. There are no exclusions or alternative route suggestions.

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