crm_lead_narrative_load

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

Annotations already indicate destructive and non-read-only behavior, and the description does not contradict this. The description adds that it routes through a domain-agent dispatcher with JWT, tenant, and company scope, which gives some operational context, but it does not describe specific side effects beyond what annotations imply.

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 plus brief parameter explanations. It is well-structured and does not include superfluous information, making it easy to read.

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?

The description fails to explain what the underlying lead_narrative_load action does, its return value, or when it should be invoked. It also does not address the output schema, leaving the tool's overall behavior incomplete for an agent to rely on.

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 Args section in the description explains message as 'free-text objective' and inputs as 'optional JSON string of structured inputs', providing basic meaning. However, it lacks detail on expected format, constraints, or examples, and the schema itself has no descriptions, so the explanation is minimal.

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 that it runs a specific CRM domain agent action and routes through a dispatcher, but it does not explain what the action actually does. The tool name hints at loading a lead narrative, but the description lacks concrete detail about the operation's effect or intent.

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 explicit guidance on when to use this tool versus alternative CRM actions like list_crm_tasks or get_crm_task. It does not mention any conditions, prerequisites, or use cases that would help an agent decide when this dispatcher is appropriate.

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