crm_prepare_lead_conversion

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

No annotations are provided, so the description carries full burden. It indicates a preparatory step for human approval, but does not disclose side effects, permissions needed, or whether state is modified. The behavioral disclosure is insufficient.

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 a single, terse sentence. While concise, it is underspecified for the complexity of the tool (nested object parameter, no schema descriptions). Key information is missing, so it does not earn its place as an adequate description.

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 lack of annotations, no output schema, and a poorly defined parameter, the description fails to provide necessary context. It does not mention return values, prerequisites, or how the change set is used afterward. The tool is inadequately documented.

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 adds no meaning beyond the input schema. The single 'request' parameter is an opaque object with additionalProperties true, and schema description coverage is 0%. The agent has no guidance on what to include in the request, making the tool essentially unusable without external knowledge.

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 'prepare linked Lead-to-Opportunity change sets for human approval,' clearly indicating the action (prepare), resource (Lead-to-Opportunity change sets), and context (for human approval). However, it does not explicitly differentiate from sibling tool crm_prepare_change, which may have overlapping functionality.

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 implies usage when converting a lead to an opportunity requiring approval, but no explicit guidance on when to use this vs. alternatives like crm_prepare_change, nor are there exclusions or prerequisites stated.

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