engage

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

Discloses draft mode (planned actions become drafts, nothing executes), hard cap on max_actions, and default action. No annotations present, so description carries burden effectively.

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 sentences, front-loaded purpose, no redundant information. Highly efficient.

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?

Covers purpose, parameters, key behavior (draft mode, defaults, cap). Output schema exists, so return values not required. Could mention output structure or comparison to similar tools, but overall sufficient.

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 has 0% description coverage, but description explains 'actions' subset and default, 'max_actions' capped, 'keywords' for search, 'account' identity. Compensates well for schema gaps.

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?

Clearly states the tool engages with tweets found via keyword search, specifies actions (like, retweet) with defaults, and distinguishes draft mode. No ambiguity.

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?

Describes context: keyword search, actions subset, draft mode default. Lacks explicit when-not-to-use or alternative tool comparisons, though siblings like queue_engagement and research_and_stage are present.

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