deep_research_plan_domain_intelligence

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

Without annotations, the description discloses little behavioral information. It mentions routing and scoping but does not state whether the action is read-only or destructive, what side effects it has, or that it returns a result (despite an output schema existing).

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 fairly concise with two short paragraphs: one for the action and routing, one for args. It is front-loaded with the tool's purpose. Could be slightly more efficient but is generally well-structured.

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 existence of an output schema, the description need not explain return values. However, it lacks details on what the 'plan_domain_intelligence' action actually produces or how the plan is used. The tool's purpose is abstract but adequately described for a planning tool.

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 description adds meaning beyond the schema by explaining 'message' as a free-text objective and 'inputs' as an optional JSON string of structured inputs. Although the schema has no descriptions, this clarifies purpose. No examples or constraints are given.

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 runs the 'plan_domain_intelligence' action within the deep_research domain agent. It specifies routing through the domain-agent dispatcher with JWT/tenant/company scope. However, it does not differentiate this from sibling tools like coding_plan_domain_intelligence beyond the domain prefix in the name.

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?

No explicit guidance on when to use this tool versus other plan_domain_intelligence tools for different domains. The description lacks usage context, prerequisites, or exclusions.

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