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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds the concrete auth scope 'Needs read:inbox', which is genuinely new and operationally useful. 'Free; changes nothing' reinforces the read-only signal that annotations already carry but adds little beyond them.

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 short clauses, lead with the action, no padding. 'Free; changes nothing' is mildly redundant with readOnlyHint/destructiveHint=false, costing a bit of tightness but not readability.

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-required-param read-only lister with full schema coverage and rich annotations, the description supplies purpose, auth scope and cost profile. Nothing essential for correct invocation is missing, though it could note how it relates to the reply/review write sibling.

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 100% and the single accountId param is fully documented in the schema (including its source, soclo_accounts_list). The description only restates that filtering by accountId is optional, adding no syntax or format meaning beyond 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 (List) and resource (reviews left on your business), which cleanly separates it from siblings like soclo_inbox_comments, soclo_inbox_mentions and soclo_inbox_messages. It does not, however, explicitly name or contrast with any sibling, so differentiation relies on the reader inferring the inbox categories.

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 phrase 'optionally filtered by accountId' implies how to narrow the result, but nothing states when to reach for this tool versus the other inbox listers or the write counterpart soclo_inbox_reply_review. Usage is inferable but not guided.

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