getAudiencesById

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly discloses the HTTP method (GET), that the operation is read-only, and the rate limit (100 requests per 1m), which is useful operational context. It does not mention auth or error behavior, but for a simple read operation this is reasonably transparent.

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 purpose, then adds rate limit and method information. Every element earns its place and there is no filler.

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 one-parameter read-only GET tool with no output schema, the description is largely complete: it gives the endpoint, the rate limit, and the read-only behavior. It omits auth/error details, but nothing critical is missing for an agent to invoke it with an ID.

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%, so the description must compensate. The endpoint '/postframe/audiences/{id}' clarifies that the single 'id' parameter is a path parameter identifying the audience, adding some meaning beyond the bare string schema. However, it does not define the ID format or any value constraints.

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 specific verb and resource: 'Get audience details', and reinforces it with the exact endpoint 'GET /postframe/audiences/{id}'. It clearly targets a single audience rather than a list, though it does not explicitly contrast itself with sibling tools like getAudiences.

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 explicit guidance on when to use this tool versus alternatives such as getAudiences or getAudiencesByAudienceIdBroadcasts. The only context provided is the rate limit and the read-only nature; no use case or selection criteria is stated.

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