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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by specifying the return shape (5-12 trend cards), the momentum scoring categories, and the outlook/opportunity/action structure. It does not cover all runtime behavior (e.g., async latency), but that is already documented in the input schema.

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 well-structured: function first, then output details, usage guidance, inputs, and attribution. It is concise and front-loaded. The final sentence 'Delivered by Manue...' is arguably non-essential, but it does not detract significantly from clarity.

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?

Given the presence of an output schema, the description does not need to restate return values. It covers purpose, output characteristics, when to use, and inputs. It could mention data sources or limitations, but for an agent selecting and invoking the tool, the description plus schema and annotations provide sufficient context.

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 100%, so the input schema fully documents all four parameters. The description only restates 'a sector to monitor and 3-8 keywords defining the watch perimeter,' which adds the phrase 'watch perimeter' but does not provide new information beyond the schema's min/max constraints and field descriptions.

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 opens with a specific verb and resource: 'Monitor emerging trends, regulatory shifts and adoption signals for a given market sector.' It adds concrete output details (5-12 trend cards, momentum score, 3-month/12-month outlook) and use cases, clearly differentiating it from sibling tools like market_research_brief or competitor_intel.

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 states when to use the tool: 'the user asks what is heating up in a market, wants to time a product roadmap or content calendar, or needs an early read on a sector.' It does not name alternative tools or exclusions, but provides clear contextual triggers.

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