crm_strategize_lead

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 through a dispatcher under JWT/tenant/company scope, but does not clarify whether this is a read or write operation, what side effects occur (e.g., lead state changes), or any permissions needed. The behavioral transparency is minimal.

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: three sentences and an argument list. It is front-loaded with the core action. However, the structure could be improved by grouping related information.

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, return values are covered. But the description fails to explain the tool's purpose in the CRM domain. It does not specify what 'strategize lead' achieves, how it affects leads, or when an agent should invoke it over alternatives. The context is incomplete for effective selection.

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 description provides basic explanations for both parameters: `message` as free-text objective and `inputs` as optional JSON string of structured inputs. This adds some meaning beyond the schema (which only lists names and types), but lacks examples, 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 `strategize_lead`' but does not explain what 'strategize_lead' entails. The purpose is unclear; it only mentions routing and scope, not the specific outcome or functionality. This does not distinguish it from 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 is provided on when to use this tool versus other CRM actions like `crm_lead_qualification` or `crm_outbound_messaging`. The description lacks context for appropriate use cases.

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