get_custom_audience

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

No annotations are present, so the description carries the full burden. It reveals some response content but does not explicitly state that the operation is read-only, what permissions are required, or how errors/rate limits behave.

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?

A single focused sentence that is front-loaded with the verb and resource, then a parenthetical list of deliverables. No filler or duplication.

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 GET with an output schema, the definition covers the core purpose and return highlights. It is incomplete on usage guidance and parameter provenance, but no elaborate behavior needs documenting.

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 the description adds no meaning to audience_id beyond its name and string type. It does not explain where the ID comes from or how to obtain it.

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?

Uses a specific verb, 'détaille', names the resource 'audience personnalisée', and enumerates the key returned aspects (taille estimée, statut, source). This clearly distinguishes from siblings that create, delete, or list audiences.

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 this is the single-audience detail counterpart to list_custom_audiences, but it never explicitly states when to use this tool versus alternatives. No exclusions or selection criteria are provided.

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