getAudiences

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

With no annotations, the description carries the burden. It discloses the HTTP method (GET), read-only nature, and rate limit (100 requests per 1m), which is helpful. However, it does not mention pagination, response shape, or any other behavioral details.

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 a single compact sentence that front-loads the core action and includes the rate limit and endpoint. Every element earns its place 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?

For a zero-parameter list tool, the description is mostly complete, but it lacks any mention of pagination or response format. The rate limit is disclosed, but an agent might still wonder about result ordering or limits.

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 tool has zero parameters, so there is no schema burden to compensate for. The description's mention of the endpoint and rate limit adds context beyond the empty schema, making this a solid score.

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 states a clear verb ('List') and resource ('audiences'), and the parenthetical 'Read-only (GET /postframe/audiences)' reinforces the operation. It is distinguishable from siblings like getAudiencesById and getAudiencesByAudienceIdBroadcasts, though it does not explicitly name them.

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 by identifying the endpoint and read-only nature, but it does not explicitly state when to prefer this over sibling tools like getAudiencesById or listCoupons. The rate limit is a useful constraint but not a usage guideline.

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