reeling_discover_community_questions

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

No annotations exist, so the description carries the full burden. It usefully discloses concrete rate limits (max 3 answers/day, 3 top-level posts/week) that an agent could not learn elsewhere, but it never states the operation is read-only, whether api_key is needed for full results, or anything about the shape of the returned threads/questions.

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?

A single front-loaded sentence with no filler, and the discovery scope leads. It does somewhat conflate two functions (searching and checking quota counters) in one line, which costs a small amount of crispness.

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?

With no annotations, no output schema, and four optional parameters, the description covers the main search and the quota limits but leaves open return format, whether quotas gate the discovery call, and what happens with missing api_key or project_id. Adequate but with clear gaps for a multi-parameter read tool.

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%, so the schema already documents keywords, subreddits, api_key, and project_id. The description names keywords and subreddits consistently with the schema but adds no syntax, defaults, or interactions beyond it.

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 (discover) and concrete resources (daily Reddit threads and Quora questions) scoped by keywords/subreddits, which distinguishes it from siblings like reeling_draft_community_answer or reeling_reply_to_comment. The secondary mention of Cadence Guard counters slightly muddies the single-function read, but the core purpose is unmistakable.

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?

'Daily' implies a recurring discovery workflow and the subreddit/keyword scoping hints at when to use it, but there is no explicit when-not-to-use or named alternative. The natural 'discover first, then draft' relationship to reeling_draft_community_answer is left for the agent to infer.

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