manage_scope_targets

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

With no annotations, the description carries the full load and delivers the key hidden behavior: 'set_target' is an upsert whose write silently overwrites existing asset tier and data sensitivity without creating duplicates, and 'remove_target' revokes scope. It omits permission requirements, reversibility of removal, and error behavior, which keeps it from a 5.

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 summary is front-loaded, then numbered instructions, then worked examples — the ordering is sound and no section is filler. Length is justified for a four-action, five-parameter tool, though emoji headers and a redundant bulleted restatement of the schema add mild noise.

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?

An output schema exists so return values need not be described, and the action semantics plus multipliers give an agent enough to call it correctly. Gaps remain: it never says which parameters are optional versus conditionally required per action (e.g. target is meaningless for 'list_targets'), and the stated 'dropdown from database' for program_id conflicts with the schema's two-value enum.

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 description coverage is 0%, so the description must compensate and does: it explains action values, target formats (URL and IP:port examples), all three asset_tier levels with their multipliers, and all four data_sensitivity levels with multipliers. This is meaning the bare enum schema cannot convey.

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 first two lines give a specific verb set and resource: add/upsert, delete, list and verify URLs/Assets within a Program's test scope. The scope ('theo Program') distinguishes it from program management or pipeline execution siblings. No explicit sibling comparison, but the resource is distinct enough to select correctly.

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?

Each of the four actions is defined in normal language (upsert, revoke, check, enumerate), and Example 3 states a clear trigger condition — run 'verify' before executing the pipeline. This gives real when-to-use context even though no action is explicitly excluded or contrasted with a sibling tool.

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