scope_manage

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

No annotations are provided, so the description must disclose behavior. It does explain the output format ('Dict with status and the resulting scope snapshot') and prerequisites ('Only add targets you have written authorization to test'). However, it does not disclose side effects of destructive actions like 'clear' or whether set_engagement overwrites existing scope. With no annotations, this gap is notable.

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 structured with headings and is generally front-loaded with the primary purpose. However, it contains redundancy, e.g., OUTPUT_DESCRIPTION and Returns say nearly the same thing, and the TOOL_NAME/DISPLAY_NAME lines are unnecessary metadata. Overall, it's readable but could be trimmed.

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 8 params, no schema descriptions, and no annotations, this description is exceptionally complete. It includes use cases, instructions, examples, prerequisites, related tools, parameter semantics, and output format. The only minor gap is explicit alternative-selection guidance, but the RELATED_TOOLS line helps.

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 fully compensates by providing an Args section that explains each parameter: action, targets, client, authorized_by, ticket, start_date, end_date, notes. This adds meaning beyond the bare schema types and helps the agent invoke the tool correctly.

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 sentence 'Manage the authorized engagement scope (the master authorization gate)' clearly states the tool's verb and resource. The USECASE further details it: 'Declare which targets are authorized, set engagement metadata, and review current scope.' This distinguishes it from sibling scanning tools by positioning it as the authorization gatekeeper.

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 clear usage context through INSTRUCTIONS and PREREQUISITES, e.g., '1. Use action=set_engagement with client/authorized_by/ticket, 2. action=add with targets you are permitted to test, 3. action=show to review.' It also lists RELATED_TOOLS like nmap_scan, generate_report, session_summary. However, it doesn't explicitly say 'use this instead of X when...' or provide exclusion criteria, so it falls short of a 5.

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