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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value beyond those by disclosing output structure (consensus score, sentiment mix, key themes, platform breakdown) and interpreting results (e.g., high consensus signals established narratives). It also cites the data source (Stratalize AI citation composite), which is useful behavioral context. No contradiction with 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?

The description is appropriately front-loaded with the usage statement and is not overly verbose. The example is detailed but informative, contributing to understanding. However, the example length slightly increases the overall bulk, so a 4 is appropriate.

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 description covers usage context, expected outputs, and an illustrative example, and it does not have an output schema to lean on. It lacks explicit mention of the 'category' parameter and does not address potential limitations or edge cases, but it is sufficiently complete for an agent to select and invoke the tool correctly. The missing parameter documentation keeps it from a 5.

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 0%, so the description must compensate for parameter meaning. It explains 'topic' well through examples ('AI in healthcare') and the phrase 'vendor, category, trend, or business topic,' but it does not clarify the optional 'category' parameter or how it modifies the query. This partial compensation justifies a mid-range score.

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 a specific verb ('researching') and resource ('how AI systems characterize a topic') across multiple platforms. It distinguishes itself from siblings by focusing on consensus across AI systems, and it enumerates the outputs (consensus score, sentiment mix, key themes, breakdown).

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 researching...' which provides explicit usage context. It also offers an example interpretation, but it does not explicitly state when not to use this tool or name alternatives, so it falls short of a full 5.

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