osint_investigate_infrastructure_start

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

The description adds async behavior and degradation when unprovisioned, going beyond annotations. Annotations already indicate non-readOnly and non-idempotent, so the description complements without contradiction.

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?

Two concise sentences: first states purpose, second provides usage guidance and next action. No unnecessary words.

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?

Given the tool starts an async investigation, the description covers input type, async behavior, unprovisioned handling, output (investigationId), and next step. Output schema likely details the return, so this is 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?

The schema has 0% coverage (only type/length), but the description adds that the query is a domain, IP, or org, providing meaningful semantics beyond 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 clearly states the tool starts an async deep-infrastructure OSINT investigation for a query, specifying domain, IP, or org as input. It distinguishes from siblings like osint_investigate_domain_start by specifying 'deep-infrastructure'.

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 notes 'Operator-deploy only; degrades to info when unprovisioned,' providing deployment context. It also tells the agent to poll with osint_investigation_status after receiving an investigationId, giving a clear next step.

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