crm_plan_sequence

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

With no annotations, the description must disclose behavioral traits. It mentions routing under JWT/tenant/company scope, but this is generic. There is no information about side effects, permissions, rate limits, or what happens upon success/failure.

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 front-loaded with the action name. Arg descriptions are separate. While efficient, the routing detail is arguably unnecessary for an agent, slightly reducing conciseness.

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 could rely on it for return values, but it does not mention what the tool returns or how the result relates to the CRM domain. The context of 'plan_sequence' within CRM is not explained, leaving gaps.

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 coverage is 0%, so the description must explain parameters. It provides basic explanations: `message` as 'free-text objective' and `inputs` as 'optional JSON string of structured inputs'. While helpful, it lacks specifics on expected formats or constraints.

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 `plan_sequence`' but does not clarify what `plan_sequence` does or its purpose. It focuses on routing infrastructure rather than the tool's intended outcome, leaving the agent uncertain about its use.

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 alternatives like `crm_plan_domain_intelligence` or other CRM tools. The description lacks any context about scenarios, prerequisites, or exclusions.

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