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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the '[read-only]' tag is largely redundant. What the description does add beyond annotations is the shape of the returned object ('keywords, texts, link, cap and counts') and the underlying GET endpoint, which is useful since no output schema exists, but it says nothing about 404/403 behavior for a missing or inaccessible trigger.

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 short, front-loaded sentences with no wasted wording; the return-field list comes before the parenthetical implementation note. The bracketed '[read-only]' prefix is the only mild redundancy against the annotations.

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 two-parameter read tool with no output schema, the description gives a rough field inventory, which is the main thing an agent needs. It stops short on ambiguous items ('counts') and on failure modes, leaving gaps that a missing output schema makes more consequential.

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 only 50%: brandId is well documented in the schema, but `id` has no description at all and the description does not clarify that it is the growth-trigger identifier (versus a post or comment id). Given the coverage gap, the description should compensate and does not.

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 and its singular scope ('One trigger') and enumerates the payload fields, which distinguishes it from list_growth_triggers even though the verb is elided to a bare noun phrase. An agent can tell this fetches one trigger by id.

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 guidance on when to use this versus list_growth_triggers or get_growth_trigger_stats, and no note that an id is required to have come from the list call. The singular framing implies per-record lookup, but that is inference rather than stated guidance.

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