Delimit Social Target Config

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

Annotations only state readOnlyHint=false and destructiveHint=false, which is generic. The description adds precise behavioral detail: actions 'update' and 'add_subreddits' write to the config, while 'status' and 'detect' are read-only. This is exactly the kind of side-effect transparency an agent needs.

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 compact, well-organized into labeled sections, and every sentence earns its place. It front-loads the core purpose before moving to usage, exclusions, sibling contrast, and side effects without repetition.

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 5 optional parameters, full schema coverage, and an output schema, the description covers the essential decision points: when to use, when not to use, sibling relationships, and side effects. A small gap is that the 'detect' action's exact behavior is not elaborated, but the schema and output schema cover enough for successful invocation.

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 baseline is 3. The description adds value beyond the schema by mapping action values to behavior (write vs read-only) and clarifying the purpose of subreddit configuration. It does not fully describe every parameter interaction, but it meaningfully supplements the schema.

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 action and resource: 'Configure social target scanning platforms' and elaborates with inspect/update platforms and add subreddits. It explicitly distinguishes this tool from delimit_social_target, which runs scans, so an agent can immediately tell them apart.

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 gives explicit when-to-use guidance ('to inspect / update which platforms...'), when-not-to-use guidance ('to run a scan...'), and names the correct alternative tools. The sibling contrast line reinforces the routing decision without ambiguity.

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