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

Annotations already disclose readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds useful context that it pulls from other organizations and requires an API key, but does not explain the non-read-only side effects (e.g., whether recommendations are persisted or state is changed).

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 three compact sentences with the core action front-loaded. Minor jargon ('OTP Scout', 'OOS') is not explained, but there is little wasted text.

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?

It covers the core purpose and external-data/API-key context, and the annotations cover safety signals. However, with no output schema, the description should more explicitly describe what is returned (recommendations? claims?) and whether invoking the scout has any persistent side effects.

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?

There is only one optional parameter, and schema description coverage is 100%, so the schema fully documents 'limit' with its default. The description adds no additional parameter meaning, which is acceptable given complete schema coverage.

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 action (run the OTP Scout) and resource (coordination intelligence from other organizations), and explains it analyzes OOS gaps and finds adoptable claims. It is clear on its own, but does not explicitly distinguish itself from the sibling search_intelligence, which likely overlaps.

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?

Usage is implied through 'discover' and 'claims you might want to adopt,' but there is no explicit when-to-use or when-not-to-use guidance, nor is search_intelligence named as an alternative. 'Requires API key' is a prerequisite rather than a usage rule.

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