socials_engage_post

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly warns that actions are toggles and 'calling again may undo', which is a critical side-effect. It omits other potential details like auth/rate limits, but the key mutation behavior is transparently disclosed.

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 short sentences, each adding essential information: the purpose, the data source, and the toggle caveat. No redundancy or filler; the structure is front-loaded and instantly scannable.

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 tool is simple (3 parameters, no output schema) and the description covers purpose, usage, and the key toggle behavior. It could mention what happens after execution (e.g., return value or error handling), but given the tool's simplicity and full schema coverage, it is sufficiently complete for correct use.

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% and all parameters have descriptions. The description adds value by explaining that 'actions' are toggles and by directing that post_id should come from socials_get_feed, which enhances the meaning beyond the raw schema.

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 opens with a specific verb ('Engage') and resource ('a tweet'), explicitly listing the supported actions: like, repost, bookmark, share. It clearly distinguishes from sibling tools by focusing on engagement with existing tweets, as opposed to creation (socials_create_post) or LinkedIn engagement (socials_linkedin_engage).

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 clear when-to-use guidance: 'Pass post_id from socials_get_feed' ties usage to a concrete workflow, and 'Only use when the user explicitly wants these actions' sets an explicit condition. It does not name alternative tools for when-not cases, but the context is sufficient.

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