delimit_social_post

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

With no annotations, the description carries the full burden. It discloses key behaviors: auto-triggering, auto-generation when text is empty, category constraints, and platform-specific tone rules. It does not cover error handling or permissions, but the provided context is rich and actionable.

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 well-structured with headers and clear sections, but it is relatively long. Some content, like the platform tone rules, could be condensed. While informative, it could be more concise without losing key guidance.

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 tool's complexity (8 parameters, platform-specific behavior, approval workflow), the description covers most necessary context: when to use, tone rules, limits, and auto-triggering. It does not mention output schema or error handling, but the output schema exists, so that's acceptable. Overall, it's complete enough for an AI agent to use effectively.

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 input schema has 100% description coverage, so the baseline is 3. The description adds value by clarifying that leaving 'text' empty triggers auto-generation and listing example categories. However, it does not significantly enhance parameter understanding beyond the schema descriptions.

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's purpose: posting to social media. It specifies it's a 'Pro' feature and outlines categories. While it doesn't explicitly differentiate from siblings like `delimit_social_generate`, the focus on posting and the auto-trigger rule imply its unique role. The purpose is clear but could benefit from a direct comparison.

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 strong usage guidelines, including an auto-trigger rule that instructs the AI to post immediately without asking for approval, daily post limits, and platform-specific tone rules. It does not explicitly list when to avoid using the tool, but the context is sufficient for decision-making.

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