get_audience_brand_names

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: "Supports pagination" and "Free (0 credits)". This goes beyond the annotations by disclosing pagination and cost behavior.

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 concise, front-loaded with the core purpose, and includes two additional useful facts (pagination and cost) in short, clear sentences. No wasted words.

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 tool with only 2 optional parameters, an output schema, and annotations, the description covers the essential context: purpose, pagination, and cost. It does not describe the return format, but the output schema handles that. Missing maybe an explicit note on typical use cases, but overall sufficient.

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 100%, with both 'search' and 'offset' parameters having descriptions. The tool description's phrase "Search audience brand names" aligns with the 'search' parameter description but does not add new meaning beyond the schema. The mention of pagination complements the 'offset' parameter but is not a parameter-specific semantic addition.

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's purpose: "Search audience brand names for Instagram audience filters." This uses a specific verb (search) and resource (audience brand names), but does not explicitly differentiate from similar sibling tools like get_brands or get_audience_brand_categories.

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 phrase "for Instagram audience filters" provides clear context for when this tool would be used. However, there is no explicit mention of alternatives or when not to use it, so it lacks explicit exclusions.

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