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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the '[read-only]' prefix merely repeats that. The description does add useful context — the endpoint wrapped (GET /api/v2/growth-triggers), what a trigger semantically is, and that active status and counts are surfaced — but says nothing about pagination, result caps, or ordering.

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?

Two sentences with the purpose front-loaded and the endpoint wrapper kept as a short parenthetical. The '[read-only]' tag duplicates the annotation and is dead weight, but the rest is tight.

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 a single optional, fully documented parameter and read-only annotations, the main remaining burden is return shape, since no output schema exists. The description mentions active status and counts but omits the other likely fields (keyword, reply/DM targets) and any volume or paging expectations.

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 coverage is 100%; the brandId property already documents the 'personal' value, the default of the key owner's active brand, and the 403 behavior for brand-bound keys. The description adds nothing about brandId, so the schema does all the work and the baseline of 3 applies.

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 names the resource precisely (the brand's keyword triggers) and explains the domain concept: a comment matching a keyword gets a public reply and/or a DM, plus active status and counts. It never distinguishes this listing tool from its close siblings get_growth_trigger and get_growth_trigger_stats, so the agent must infer the difference from names alone.

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 when-to-use guidance. The agent is not told to call this to discover trigger IDs before calling get_growth_trigger, update_growth_trigger, or delete_growth_trigger, nor when to prefer get_growth_trigger_stats over this tool for metrics. Usage is only implied by the verb 'list'.

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