Delimit Social Post

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

Discloses side effects (queuing when draft=True, immediate posting otherwise), rate caps with environment overrides, and approval-email behavior with registry_draft_id. Annotations only say readOnlyHint=false and destructiveHint=false, so the description adds substantial operational context. It does not contradict the annotations.

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 bullets, but it is overlong and repeats the rate cap and auto-trigger rule nearly verbatim. A leaner version would be easier to consume, though the key information is front-loaded.

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 when to use, when not to use, side effects, approval flow, rate caps, categories, and per-platform tone. The only material gap is the platform inconsistency between the prose ('Twitter / Reddit', LinkedIn rules) and the schema's twitter-only platform parameter; otherwise an agent has enough to invoke correctly.

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 already covers all 8 parameters at 100%, so the baseline is 3. The description adds useful category values and auto-generation behavior, but its platform guidance (Reddit/LinkedIn tone rules) conflicts with the schema's platform parameter description ('Social platform (twitter)'), which keeps it from rising above baseline.

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?

Opens with 'Post to social media (Twitter / Reddit) (Pro)' — a specific verb and resource — and immediately contrasts with delimit_social_generate and delimit_social_history, so an agent can tell this is the actual posting tool. The sibling contrast removes ambiguity about what this tool is not.

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?

Contains dedicated 'When to use' and 'When NOT to use' sections, names the alternatives (delimit_social_generate, delimit_social_history, delimit_social_approve), and encodes an explicit auto-trigger rule. This is unambiguous routing guidance beyond anything the schema provides.

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