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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no indication of how many topics are returned, whether the list is cached/static, or what a topic record contains, which matters because the next step presumably needs topic identifiers.

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 front-loaded sentence with no filler or redundancy. It is efficient, but its brevity is also the source of the gaps in usage and behavioral detail.

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?

With no parameters, no output schema and annotations covering the safety profile, the definition is minimally viable. The missing piece is return-value shape: an agent doesn't know if topics come back as plain strings, IDs, or objects, which is precisely what it would need to feed a subsequent create_bombora_audience call.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless global lookup rather than something scoped to an account or audience.

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?

Specific verb+resource ('Get available intent topics') with the downstream purpose (BOMBOORA audience creation) named. It is distinguishable from the many create_* audience siblings because it clearly retrieves reference data rather than mutating anything, though it doesn't explicitly contrast with lookup siblings like get_abm_account_lists or search_target_group_criteria.

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 BOMBOORA audience creation' implies the call is a prerequisite step when building a Bombora audience, which is useful context. However, it never states when to call it versus other lookups, whether it must precede create_bombora_audience, or any prerequisites.

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