delimit_social_target_config

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

With no annotations, the description fully discloses behavioral differences: actions like 'update' and 'add_subreddits' are writes, while 'status' and 'detect' are read-only. This is valuable, though it could mention if updates are destructive or require permissions, but overall it's very transparent.

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 concise and well-structured: purpose statement, usage guidelines, sibling contrast, and side effects. Each sentence adds important information without redundancy.

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 has 5 parameters with 100% schema coverage and an output schema, the description provides complete context: what the tool does, when to use it, how it differs from siblings, and behavioral side effects. No obvious gaps.

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 baseline is 3. The description adds value by grouping actions into read/write categories and explaining the purpose of each action beyond the schema's short descriptions. This helps the agent understand parameter usage contextually.

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 states a specific verb and resource ('Configure social target scanning platforms') and further clarifies it is for inspecting/updating platforms and adding subreddits. It distinguishes from siblings by noting that delimit_social_target runs scans, while this tool configures platforms.

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?

Explicitly provides when to use (inspect/update platforms, add subreddits) and when not to use (running scans or drafts), with specific sibling alternatives (delimit_social_target, delimit_social_generate). This gives clear guidance for tool selection.

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