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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context about the output type (consolidating/fragmenting), citation evidence, and a concrete example, going beyond the annotations.

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 sentences, front-loaded with usage guidance, then output description, example, and source. Every sentence earns its place with no redundancy or 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?

The tool is simple (one parameter, no output schema), and the description covers what it returns (signal type, citation evidence), use cases, and a concrete example. This is sufficient for an agent to invoke it correctly, though it could add a note about how the signal is calculated or typical categories.

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 0% and the schema only says 'category' is a string. The description implies the parameter is a software category name via the example 'HR tech', which adds some meaning, but it does not explain acceptable values or formatting beyond the single example.

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 ('assessing') and resource ('software category maturity', 'market entry', 'consolidation risk'), and clearly identifies the output as a market structure signal. It distinguishes itself from sibling tools by focusing on consolidation/fragmentation signals.

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?

Provides explicit use cases ('Use when assessing...') but does not mention when not to use it or name alternative tools. The context is clear enough for an agent to select it appropriately among many siblings.

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