research_and_stage

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

Given no annotations, the description fully discloses the tool's behavior: it searches keywords, keeps relevant tweets via a keyless heuristic, writes persona-aware replies, stages one draft per tweet, and does not post. It also notes the required settings block.

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?

The description is concise (three sentences), front-loaded with the main action, and each sentence adds value without waste. It is well-structured for quick parsing.

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?

The description covers the tool's purpose, flow, preconditions, and post-conditions. It omits parameter details but given the output schema exists and the description is otherwise thorough, it is nearly complete.

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 0%, so the description must compensate. It mentions keywords and implies the action but does not explicitly explain the 'account' and 'max_items' parameters. It adds some meaning but not complete per-parameter guidance.

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?

The description clearly states the tool searches keywords, keeps relevant tweets, writes replies with the LLM, and stages drafts. It distinguishes itself from siblings by emphasizing that nothing is posted and points to list_drafts for review.

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 explicitly states when to use (to research and stage replies) and when not (nothing is posted), provides alternatives (review with list_drafts), and mentions a prerequisite (requires 'llm' block in settings).

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