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

With no annotations, the description carries the behavioral burden and does disclose the key trait 'Read-only' plus the categories of information returned. It does not cover permissions, pagination, or error behavior, but for a simple read-only panel this is substantially transparent.

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 very concise and front-loads 'Read-only' before listing return-content categories. It is structured as fragments rather than complete sentences, but there is no 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?

For a one-parameter tool with no annotations and no output schema, the description adequately lists returned information and read-only behavior. However, it leaves the required search_id undocumented and provides no usage guidance, so it is only minimally complete.

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%, and the description never mentions the required search_id parameter. The parameter name and UUID format in the schema convey basic identity, but the description adds no meaning about what the search ID scopes or expects.

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 read-only and specifies the review-panel content it exposes: uncertain contacts, last run results, totals, and next scheduled run. That is more specific than a tautology, though it does not explicitly differentiate this panel from the sibling sdr_icp_review_run.

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?

It says 'Read-only' but gives no explicit guidance on when to use this panel versus sdr_icp_review_run or other ICP review tools. There are no when-to-use conditions, exclusions, or alternatives named.

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