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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds useful context beyond annotations by defining the shape of the return (metadata fields only, not full layouts), which steers the agent away from expecting layout data. It doesn't mention pagination or rate limits, hence not a 5.

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?

One sentence for what it returns, one sentence for the alternative. Zero waste, front-loaded with the resource and the metadata-only scope.

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, read-only list tool with no output schema, the description covers purpose, scope, and the alternative lookup tool. Missing only minor operational details like pagination or result ordering, which are not critical here.

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 coverage is 100% and the schema itself documents product_id, including a pointer to sonar_list_products. With only one parameter fully documented in the schema, the baseline is 3; the description adds no new parameter detail, but the single-param and fully documented nature keeps it above baseline. Slight lift because it clarifies product scoping in prose.

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 (List) and resource (app-store screenshot sets), and explicitly scopes the output to metadata only, enumerating the fields. It names the sibling sonar_get_screenshot_set for full layouts, so the agent can distinguish it from get_screenshot_set and create/update_screenshot_set without opening schemas.

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?

Explicitly names the alternative (sonar_get_screenshot_set) and the condition that selects it (when full layouts are needed). The verb 'list' plus the 'metadata only' qualifier makes the when-to-use boundary clear.

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