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

Annotations already cover readOnly/idempotent/closed-world, so the bar is lower; the description still adds that results are 'Ranked by fit and heat' and that 'Nothing is ever posted automatically', which reassures the agent this is a safe, non-mutating read. It doesn't describe pagination or result size behaviour.

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 tight sentences with the resource description front-loaded and the workflow handoffs after. Minor redundancy between 'Ranked by fit and heat' and the schema's sort=best description, but no wasted framing.

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?

No output schema exists, but the description tells the agent what kinds of items come back (threads, posts, comments) and that they are ranked, which is enough to interpret results. Filtering semantics are left wholly to the schema, which is acceptable given full coverage.

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 sort, agent, limit, status and business_id are all already documented in the schema. The description only echoes the ranking concept behind the default sort and adds nothing about syntax or how to combine filters, so baseline 3 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?

States a specific verb (read/list) and resource (Reddit, LinkedIn and X conversations), and pins down what an opportunity actually is: threads, posts and comments where the business can genuinely help. This differentiates it cleanly from siblings like draft_reply and update_opportunity.

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?

Names the downstream tools and their roles — 'Use draft_reply to write an answer and update_opportunity to record what happened' — which routes the agent through the workflow. It doesn't explicitly state when to pick this listing over filtering alternatives, but the sequencing guidance is clear.

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