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

Annotations already declare readOnlyHint=true, and the description aligns by stating it returns a deliverable. It adds context about server-side validation and a reference case. However, it does not disclose additional behavioral traits like response format, pagination, or rate limits beyond what annotations 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 four sentences, but the first part is cryptic ('Gapup agent-payable C-suite expertise (CMO)') and the reference case may be too specific. It is not as concise as it could be, and the structure could front-load the core purpose more clearly.

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 6 parameters, 4 required, and no output schema, the description should explain the deliverable structure and handling of the async parameter. It mentions none of these, leaving critical gaps for an AI agent to correctly invoke the tool.

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 only 17% (only async has a description). The tool description does not add meaning to the other 5 parameters (brand, channels, industry, keywords, historicalCrises). It briefly mentions 'send the documented case fields' but does not explain individual parameters, leaving a significant gap.

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 the tool is a reputation engine that returns a structured, audited deliverable, with a specific reference case. The verb 'returns' clarifies the action. However, it does not differentiate from potential sibling tools like sentiment_news_pulse or brand_equity_voice_share_calculator.

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 provides no explicit guidance on when to use this tool versus alternatives. It mentions 'Gapup agent-payable C-suite expertise (CMO)' which vaguely suggests context but does not specify when-not or provide exclusions.

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