reeling_draft_community_answer

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

With no annotations, the description carries the full burden. The word 'Draft' usefully signals this does not publish, and 'verified by Reeling's Spam Shield' discloses a validation step, but it says nothing about whether the draft is persisted, what permission/auth is needed (api_key is described as optional in the schema only), or any rate limits.

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 sentence with the action, target resource, and quality constraint front-loaded. Nothing is wasted or buried.

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 6-parameter generation tool with no output schema and no annotations, the description is thin. It does not say whether the returned draft is saved server-side, whether it can be passed straight to reeling_publish_post, or how strictly the Spam Shield changes the output.

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 applies. The description only echoes the platform enum (Reddit/Quora) and adds no meaning about subreddit, project_context, question_snippet, or the optional api_key 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?

Specific verb plus resource: 'Draft a ... answer for a Reddit thread or Quora question.' That is clearly different from reeling_check_spam_score or reeling_discover_community_questions, but the description never names those siblings or explicitly places this tool after discovery, so differentiation is implied rather than stated.

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?

Usage is only implied: an agent can infer this is the drafting step that follows question discovery, and the Spam Shield mention implies the output is pre-validated before publishing. There is no explicit when-to-use, when-not-to-use, or named alternative such as reeling_check_spam_score or reeling_publish_post.

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