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

Annotations already declare readOnlyHint=true, and the description adds behavioral details beyond that by outlining the return values and providing an interpretive example (e.g., 'GROWING trend' from consecutive citation increases). This gives the agent a sense of what to expect without contradicting the read-only nature.

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 description is three sentences, front-loaded with the use case, followed by output details and an example. It is efficient and every sentence adds value, though the example could be slightly trimmed without losing meaning.

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 single-parameter tool with no output schema, the description covers usage, return values, an example, and data source. It is reasonably complete, though it could clarify output formatting or edge cases, but for this simplicity level it is sufficient.

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 schema has one parameter (brand_name) with zero description coverage, so the description must compensate. It implies the parameter's meaning via the word 'brand' and the example 'HubSpot', but it does not explicitly define what brand_name accepts or any format constraints. This is adequate but not thorough.

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 the tool's function: monitoring vendor brand trajectory and competitor momentum. It specifies the output (4-week momentum score, trend direction, weekly movement series) and provides a concrete example, distinguishing it from sibling tools focused on other metrics.

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 description explicitly opens with 'Use when monitoring...' and 'or tracking...', giving clear usage scenarios. It does not mention alternatives or exclusions, but the scenarios are specific enough to guide the agent toward this tool versus generic 'get_' siblings.

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