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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is largely covered. The description adds that the tool returns scan counts, errors, source health, and schedules, which is useful context beyond annotations. However, it does not explain pagination, cursor behavior, or result ordering, leaving a moderate gap.

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 single sentence is front-loaded and has no filler. It efficiently lists the main data categories. It is slightly broad and includes 'schedules,' which may blur scope with schedule-specific tools, but it is structurally sound.

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 list tool with 6 parameters, no output schema, and zero schema description coverage, the description is too thin. It gives no filtering, pagination, or scope details beyond the returned data categories, so an agent cannot confidently construct a correct list request.

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 are 6 parameters and schema description coverage is 0%, so the description carries the full burden for parameter meaning. It mentions none of the parameters: limit, cursor, status, platform, workspace, or competitors. The agent cannot infer how to filter or paginate from the description.

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 clear verb and resource: reading competitor scan history. It names the data returned (counts, errors, source health, schedules), which helps identify the tool. It does not distinguish this list operation from sibling write tools like competitor_scans_start, but the read/list intent is still clear.

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?

There is no explicit guidance on when to use this tool versus alternatives such as competitor_scans_start or competitor_ads_list. The agent can infer it is for reading scan history, but no exclusions, prerequisites, or selection criteria are given.

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