delimit_social_approve

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It fails to explain what the 'approve' action actually does (e.g., posts immediately or schedules?) or what 'reject' does (permanently deletes?). The '(Pro)' label hints at a feature gate without elaboration, and there is no mention of required permissions or side effects.

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 two sentences long, with the first sentence clearly stating the tool's purpose and the second providing a key usage hint. Every word earns its place; no fluff.

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?

For a tool with a simple interface (2 params, clear actions) and an existing output schema, the description covers the essential workflow and usage. It lacks details on errors or success/failure outcomes, but given the tool's simplicity and output schema, it is nearly complete.

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%, so the schema already documents both parameters. The description adds no additional meaning beyond the schema: it merely restates the actions without detailing parameter constraints, types, or formats. Baseline score of 3 is appropriate.

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 'Manage social media drafts: list, approve, or reject (Pro).' It specifies the resource (social media drafts) and the actions (list, approve, reject), distinguishing it from sibling tools like delimit_social_post which focuses on posting, and delimit_social_generate which generates content.

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 explicit usage guidance: 'Use with delimit_social_post(draft=True) to queue content for review.' This tells the agent when to use this tool (after queuing drafts) but does not explicitly state when not to use it or list alternatives, though the workflow is clear.

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