get_audience

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

No annotations provided, so description carries the burden. It only states 'Get details', implying a read-only operation but does not explicitly declare idempotency, side effects, or permissions. For a simple read tool, it is minimally sufficient but could be more 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?

Single sentence with 17 words, front-loading the action and key output fields. Every word earns its place with no redundancy. Highly concise and well-structured.

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 output schema, the description hints at return fields (name, description, phone number column name), which helps the agent understand what to expect. However, it does not mention error handling, empty results, or full output structure. For a simple tool, this is mostly complete.

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 has 100% coverage with one parameter (audience_id) described as 'The audience ID'. Description adds 'by ID' but no extra semantics about format, source, or constraints. Baseline score 3 is appropriate since schema already describes the parameter adequately.

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 clearly states the tool retrieves details for a specific audience by ID, listing specific fields like name, description, and phone number column name. This distinguishes it from siblings like get_audiences (list) and get_audience_members (list members).

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?

No explicit guidance on when to use this tool versus alternatives. The name and description imply it's for single audience details, but it does not mention get_audiences for listing or when not to use it. Adequate but lacks explicit context for selection.

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