sovereign_scan_onboarding_radar

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

The description explicitly discloses that the scan is 'strictly read-only' and uses os.scandir, which is valuable behavioral context beyond the schema. It also mentions a time budget (max_scan_seconds) and the 60-second radar concept, giving the agent a sense of bounded execution. However, it does not describe what happens on timeout or whether results are persisted.

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 a single sentence that packs the tool's purpose, method, and scope efficiently. It is front-loaded with the action and resource. Slightly dense with the ADR-08 reference and directory list, but nothing is wasted.

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 read-only discovery tool with 100% schema coverage, the description is largely complete. It explains what the tool does, how it does it (os.scandir), and its safety profile (read-only). It lacks explicit output/return format details, but since there is no output schema, a brief note on what the ranked results look like would have made it 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 description coverage is 100%, so the schema already documents both parameters. The description adds the 'strictly read-only' and '60-second' context but does not add new meaning about the parameters themselves. Baseline 3 is appropriate.

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 names a specific verb ('Runs'), a specific resource ('ADR-08 60-Second Auto-Discovery Onboarding Radar'), and the exact outcome: discover, classify, and rank domain knowledge directories. It also lists the target directory categories, which distinguishes it from sibling tools like sovereign_search_vault or sovereign_inspect_archive.

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 implies this is an onboarding/discovery scan for domain knowledge directories, but it does not explicitly state when to use it versus alternatives like sovereign_search_vault or sovereign_optimize_context. The context is clear enough for an agent to infer the use case, but no explicit when/when-not guidance is provided.

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