osint_investigate_supply_chain_start

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

The description discloses that the tool is async and returns an investigationId immediately. Annotations already indicate openWorldHint=true and not read-only, but the description adds no further behavioral details about side effects or external dependencies.

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?

Three sentences, front-loaded with purpose, no fluff. Every sentence adds value: purpose, deployment caveat, async behavior.

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?

The description covers the essential: async operation, immediate return of ID, and polling method. It mentions operator-only deployment. However, it lacks parameter guidance and doesn't elaborate on the output schema despite context signals indicating an output schema exists.

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?

The only parameter is 'query' with schema showing maxLength 253 but no description. The description merely says 'for a query' without explaining what constitutes a valid supply-chain query (e.g., domain, company name). With 0% schema description coverage, the description should add more context.

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 verb 'Start', the resource 'supply-chain OSINT investigation', and specifies it's async. It distinguishes from sibling tools like osint_investigate_domain_start by explicitly naming 'supply-chain'.

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 says 'Operator-deploy only; degrades to info when unprovisioned,' providing clear context on deployment requirements. It also explains the async polling pattern. However, it does not explicitly state when not to use this tool versus other investigation start tools.

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