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

The annotations already declare this as a non-destructive read-only operation, and the description adds useful domain context by defining 'reviews' as all reviews and 'shown' as excluding hidden and pending reviews. It also discloses that sync state and associated widgets are included, which is meaningful beyond the annotations.

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 a single compact sentence with no wasted wording, and the key field definitions are packed into the parenthetical. Its sentence-fragment style and nested parentheses slightly reduce clarity, but it remains front-loaded and efficient.

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 zero-parameter list tool with no output schema, the description covers the important returned concepts: review sources, review counts, sync state, and associated widgets. It omits ordering or pagination details, but those are minor for this simple read-only listing.

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?

The tool takes zero parameters, so there is no parameter semantics to document. The description does not need to compensate for schema gaps, and the baseline for a zero-parameter tool applies.

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 identifies the resource (review sources) and the aggregate data returned (review counts, sync state, widgets that show them). It is a noun phrase rather than a verb-led statement, but the plural resource and bundled metadata clearly distinguish it from the singular get_review_source.

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 when-to-use guidance, no prerequisites, and no comparison to alternatives such as get_review_source or list_widgets. An agent can infer that this lists all review sources, but the description does not route it against sibling tools.

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