crm_icp_intelligence

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits such as side effects, return values, rate limits, or whether the action is read-only or mutating. The action 'icp_intelligence' is not described, leaving the agent blind to its behavior.

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 two sentences and bullet points for args. However, it is not front-loaded with the most critical information (what icp_intelligence does). The routing detail could be omitted or placed later. Acceptable but not optimal.

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 simplicity (2 params, no required, output schema exists), the description should clarify the purpose of icp_intelligence and what the output contains. It fails to do so, leaving an information gap. The presence of an output schema does not compensate for the missing action explanation.

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?

Schema description coverage is 0%. The description adds minimal meaning: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs.' It does not specify format, constraints, or examples. The value added over the schema is low.

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 'Run the crm domain agent action icp_intelligence' but does not explain what icp_intelligence does. The term is domain-specific and unclear to an agent. The purpose is vague and does not distinguish from sibling tools like crm_plan_domain_intelligence.

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 mentions routing through the domain-agent dispatcher under JWT/tenant/company scope, which gives authentication context, but provides no guidance on when to use this tool vs alternatives, nor when not to use it. There are no explicit usage guidelines.

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