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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses the methodology ('citation volume patterns') and even names the source ('Stratalize citation volume heuristics'). It also explains the output format (score with evidence strings), adding behavioral context that annotations alone do not provide.

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 compact and front-loaded with the usage scenario. Every sentence adds value: use cases, return value, example, and source. There is no fluff or redundant information.

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 it has only one parameter, no output schema, and strong annotations, the description fully covers what the tool does, how results are presented, and an illustrative example. It is sufficiently complete for an agent to invoke the tool correctly.

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 input schema has a single 'category' parameter with no description (0% coverage). The description compensates by clarifying it is a 'software category' and gives an example ('ERP category'), directly enriching the parameter semantics. While it doesn't enumerate valid values, the example and phrasing make the parameter meaning clear.

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: 'assessing whether a software category faces near-term displacement risk' and 'timing a market entry or exit decision.' It also specifies the returned value (disruption risk score 0 to 1 with evidence strings) and provides a concrete example, making the purpose unmistakable.

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 begins with 'Use when...' and explicitly lists two use cases, providing clear context for when to invoke the tool. It does not mention alternatives or when-not-to-use, but the guidance is specific enough for an agent to select this tool over siblings.

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