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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds one genuinely useful behavioral fact — the plan entitlement requirement — but omits the default scoping behavior (only active events in the last 24h unless overridden), which materially affects what a caller receives.

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?

Three short sentences, each earning its place: purpose, usage trigger, prerequisite. The capability statement is front-loaded and there is no filler.

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 zero-required-parameter, read-only list tool with an output-free contract this is close to adequate, but with no output schema and two undocumented enum parameters the description should have flagged the default active/24h narrowing. The entitlement note is good but leaves the default-result behavior unexplained.

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 only 33%: limit is documented in the schema, while status and time_range have no descriptions at all in either place. The description adds nothing about parameters, so the agent must infer that the default status=active and time_range=24h silently narrow results.

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 states a specific verb and resource with scope: listing reputation or crisis events detected for the account's monitored topics. No sibling tool covers crisis/brand-risk detection (siblings are trend, watchlist, and capability tools), so the agent can route here without opening the schema.

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?

It gives an explicit use trigger ("Use when the user asks about risks around a brand or topic") plus a prerequisite ("Requires a plan with crisis monitoring"). It does not name alternatives or when-not-to-use conditions, but none of the sibling tools overlap with this capability.

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