create_draft_reply

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a draft reply, implying a write operation that doesn't publish immediately, but fails to mention critical details: whether it requires specific permissions, if drafts are saved locally or on a server, what happens on success/failure, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and context. There is no redundancy or fluff, making it highly concise and well-structured for quick understanding.

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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., draft storage, error handling), usage context relative to siblings, and output details. While the schema covers parameters well, the overall context for safe and effective tool invocation is insufficient, especially compared to sibling tools that might offer similar or overlapping functionality.

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?

The schema description coverage is 100%, with both parameters ('content' and 'reply_to_tweet_id') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as content length limits or tweet ID format requirements. Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to given the schema's completeness.

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 action ('Create a draft reply') and the resource ('to an existing tweet'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'reply_to_tweet' or 'create_draft_quote_tweet', which would require more specific language about draft vs. published replies or reply vs. quote functionality.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'create_draft_reply' over 'reply_to_tweet' (which might publish immediately) or 'create_draft_quote_tweet' (which creates a quote tweet draft), nor does it specify prerequisites like authentication or draft limitations. This leaves the agent without context for tool selection.

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