procurement_plan_domain_intelligence

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

The description only mentions routing through a dispatcher and does not disclose any side effects, permissions, or potential destructive behavior. Despite the destructiveHint annotation, the description adds no context about what changes may occur.

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 short and to the point, but it could be better structured. It lacks detail and organization, though it does not suffer from excessive verbosity.

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 is highly incomplete. It lacks critical context about the action's function, expected input formats, output structure, error conditions, and differentiation from numerous related sibling tools. This makes it nearly impossible to use correctly without external knowledge.

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% description coverage, so the description's one-liners for 'message' and 'inputs' partially compensate. However, they remain vague (e.g., 'free-text objective' and 'structured inputs') with no format, constraints, or examples.

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 states it runs a specific domain agent action, but does not explain what the action does or its intended outcome. The purpose is implicit from the name 'plan_domain_intelligence' but not clarified, leaving the tool's function ambiguous.

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 guidance is provided on when to use this tool versus similar siblings like dispatch_domain_agent or brain_plan_domain_intelligence. There are no conditions, prerequisites, or examples given.

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