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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful ordering ('newest first') and default timeframe context, but does not describe pagination, response shape, rate limits, or auth expectations.

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 core purpose is front-loaded and the single paragraph stays reasonably tight. The long enumeration of change types is dense but useful for scoping, though it makes the sentence harder to parse.

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 feed tool with no output schema, the description should explain the returned item structure or pagination more clearly than it does. It adequately lists covered categories but leaves response shape and sibling routing ambiguous.

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 33%; the description explains the default days window but says nothing about the limit parameter, and domains is already described in the schema. It does not compensate for the undocumented limit semantics.

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 that this returns a newest-first feed of what tracked rivals changed, and it enumerates the change categories covered. It does not differentiate this feed from similar siblings such as get_significant_competitor_changes or get_predicted_competitor_moves.

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 only a default lookback of 7 days and does not explain when to use this feed versus the closely related competitor-change siblings. There are no exclusions, prerequisites, or selection guidance for days, limit, or domains.

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