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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds that the result includes both opportunities and per-improvement state, but says nothing about scoping per project/site, completeness of results, or whether articles without opportunities are included.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is part of why other dimensions are under-served.

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?

There is no output schema, 0% parameter documentation, and the description does not describe the return shape (list of improvements with states) or scoping. For a two-required-param read tool it leaves the agent with too many unknowns.

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% for two required parameters (projectId, siteId), and the description never mentions either. It should explain that the query is scoped to a project and site, but gives the agent no guidance beyond bare parameter names in the schema.

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?

States a specific verb (read) and resource (refresh opportunities for published articles plus the state of each improvement), which is clearer than the title alone. It is distinguishable from get_article or list_articles, though the term 'refresh opportunities' remains somewhat abstract without a hint of what an 'improvement' record contains.

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?

No indication of when to call this versus get_article, list_articles, or list_ctr_opportunities, and no prerequisites (e.g., whether the article must be published or the project/site must exist). The agent must infer everything from the name.

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