solver_plan_domain_intelligence

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

No annotations are provided, so the description must disclose behavioral traits. It mentions routing through a domain-agent dispatcher with JWT/tenant/company scope, which gives some authentication context, but it does not describe side effects, data modifications, or what 'plan_domain_intelligence' entails. The action's behavior remains opaque.

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 concise with a clear Args section. It avoids unnecessary detail, though it could benefit from a brief explanation of what the action does. Overall, it is well-structured and to the point.

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?

Despite having an output schema, the description lacks essential context: it does not explain the purpose of 'plan_domain_intelligence', what side effects occur, or how the output is structured. The agent cannot fully understand the tool's role or when to invoke it, given the many similar siblings.

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 coverage is 0%, so the description must compensate. It adds 'Free-text objective' for message and 'Optional JSON string of structured inputs' for inputs, providing slight meaning beyond the schema titles. However, this is minimal and does not specify format constraints or valid values.

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 for the solver domain. The verb 'Run' and specific resource are present, but it does not differentiate from the many sibling tools like coding_plan_domain_intelligence or commerce_plan_domain_intelligence, which share similar names.

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 provides no guidance on when to use this tool versus alternative 'plan_domain_intelligence' tools. No context about the solver domain, prerequisites, or exclusions is given, leaving the agent to guess.

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