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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing the option becomes marked Converted, the job defaults to Unscheduled unless a start is passed, per-call confirmation defaults on and is switchable, and that it 'reaches other people' requiring user confirmation. It also states the API key requirement.

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?

Front-loaded with purpose and effect, and each sentence carries actionable information (job cardinality, scheduling default, confirmation, people-reach, credential). It is slightly verbose with the app-comparison clause and repeated confirmation phrasing, but nothing is wasted enough to hurt.

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?

For a mutation tool with no output schema, the description covers the important behavioral facts (what is created, what is mutated, scheduling default, confirmation behavior, auth). It does not describe the returned job payload, but with no output schema that is a minor gap rather than a blocking omission.

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 100%, so baseline is 3, but the description adds meaning beyond the schema: it explains the effect of `start` on scheduling (job is Unscheduled without it) and reinforces that `option` selects which estimate line is converted. This is genuine value the field-level descriptions do not carry.

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?

States a specific verb+resource ('Turn one estimate option into a job') and clarifies it converts the named option while marking it Converted. This distinguishes it clearly from siblings like service-fusion_create_job and service-fusion_create_estimate, which lack the conversion semantics.

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?

Explains the core usage pattern ('one call creates one job; call again with another option') and references the in-app 'Convert to Job' flow, giving clear context for when to reach for it. It stops short of explicitly naming alternative tools to use instead, so no explicit exclusions are provided.

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