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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by enumerating the return payload (name, store, sample size, top complaint, link), which matters since no output schema exists. It doesn't mention pagination or how limit interacts with total results, keeping it below 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?

Three compact sentences: purpose first, filter options second, return payload last. No filler, no redundancy with the schema, and the most important information is front-loaded.

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 low-risk, annotation-covered, zero-required-parameter list tool this covers purpose, filterable dimensions, and return shape. The remaining gap is behavioral detail on result volume (pagination, what happens when limit truncates results), which the description never addresses.

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%, so the baseline is 3, but the description adds real value beyond the schema by giving concrete sector/category example values ('Banks & payments', 'Product reviews') that clarify what string to pass. It does not explain the store enum values or limit behavior beyond what the schema already documents.

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+resource ('List or search the apps that have complaint data in Revunda's studies') and names the scope of the dataset. It is clearly distinguishable from get_app_complaints and what_users_complain_about by being the discovery/catalog step, though it never names those siblings explicitly.

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?

The description explains the available filters but gives no explicit when-to-use guidance, no mention of the sibling tools, and no statement of what to call next (e.g. get_app_complaints for a chosen app). Usage is only implied by the word 'search' and the returned fields.

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