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

With no annotations, the description carries the full burden and delivers: approve_feed_item schedules to every platform, starts a render and charges credits, schedules nothing when no platform is connected, and connecting later does not retroactively publish. regenerate_content rewrites in place (same record id) and always returns a confirmation because it spends credits. These are exactly the side effects, costs and irreversibility cues an agent needs.

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?

Dense but front-loaded: it leads with the tool's purpose, then the confirmation requirement, then the two riskiest actions. Every sentence adds operational meaning, though the block is long and the per-action clauses could be tightened.

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 9 enum actions, no annotations and no output schema, the description richly covers approve_feed_item and regenerate_content but leaves reject/dismiss/publish_content/reschedule_post/retry_post/mark_as_published/boost_post nearly unaddressed. Adequate for the riskiest paths, incomplete for the rest.

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 89%, so the schema already documents the parameters, setting the baseline at 3. The description adds only marginal meaning (regenerate_content takes content_type + content_id rather than feed_item_id), which is useful but largely restates the same distinction the schema descriptions already make.

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?

States a specific verb+resource and scope: 'Run an explicit feed or post action without an AI chat turn.' It also distinguishes itself from the AI-chat path and from the confirmation sibling, so an agent can tell what this tool is for without opening the schema.

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?

Clearly routes the agent: high-impact actions return a message_id that must be confirmed via autowhisper_confirm, and it explains the approve_feed_item spend semantics. It does not contrast with other action-adjacent siblings such as autowhisper_edit_content, so usage guidance is strong but not exhaustive.

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