delimit_social_target_config

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

Without annotations, the description discloses that actions 'update' and 'add_subreddits' write to the target config, while 'status' and 'detect' are read-only. This is good behavioral disclosure, though it does not cover all aspects like authentication or rate limits. Still, it effectively communicates the tool's read/write nature.

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 extremely concise: four short sentences plus a side-effect note. It is front-loaded with the purpose and immediately guides usage. Every sentence earns its place.

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 that an output schema exists, the description need not cover return values. It covers purpose, usage guidelines, side effects, and sibling differentiation. For a configuration tool with 5 optional parameters, this is fully 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% with detailed descriptions for each parameter. The description adds context by grouping parameters into actions and explaining side effects, which helps the agent understand how parameters interact. This goes beyond the schema's individual parameter 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 configures social target scanning platforms and distinguishes from its sibling delimit_social_target which runs scans. The verb 'configure' plus the resource 'social target scanning platforms' is specific and action-oriented.

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 direct references to sibling tools delimit_social_target and delimit_social_generate. This is excellent guidance for an agent.

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