crm_competitive_positioning

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

With no annotations, the description only mentions routing through the dispatcher under JWT/tenant/company scope, lacking disclosure on whether the action is read-only, destructive, or has side effects.

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 but lacks front-loading of key information; the arg list is clearly formatted but the overall content is minimal.

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?

Even with an output schema present, the description fails to explain the action's purpose, expected outcomes, or behavior, leaving significant gaps for an agent to use it correctly.

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?

Despite 0% schema coverage, the description adds minimal meaning: 'message' is a free-text objective, 'inputs' is optional JSON string; no structure or constraints are provided 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 states 'Run the crm domain agent action competitive_positioning' which indicates a specific verb and resource, but does not explain what competitive positioning does, making it vague compared to sibling CRM tools.

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 on when to use this tool versus alternatives like crm_competitor_watchlist or crm_assess_pipeline; no when/when-not advice is provided.

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