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

Annotations already cover readOnly, idempotent, and non-destructive behavior, so the description is not required to restate those. It adds tenant-scoped context and enumerates the domain objects, which is helpful, but it does not explain what 'convert to bid' actually does or what the output represents.

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 sentence with no filler, so it is concise, but it sacrifices substance. It front-loads a vague verb and a long list of object types without structuring the key action or differentiating context.

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 13 parameters, nested objects, an output schema, and many sibling tools, this description is far too thin. It leaves the conversion purpose, parameter relationships, and workflow context unexplained, so an AI agent cannot reliably select or invoke this tool correctly.

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 description coverage is only 15%, and the description adds essentially no parameter-level meaning. The 'tenant-scoped' phrase aligns with tenant_id, but critical parameters such as line, lines, query, bridge, format, approval, source_id, document_id, estimate_id, progress_pct, and idempotency_key remain unexplained.

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 uses the generic verb 'Operate on' and lists OCE Estimator/Appraiser objects, but it never states the specific action of converting an estimate to a bid. It also does not distinguish this tool from sibling estimator_estimate_convert_to_invoice; only the tool name carries the conversion 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?

No guidance is provided on when to use this tool versus alternatives such as estimator_estimate_convert_to_invoice or other estimator tools. There is no mention of prerequisites, input state, or which workflow should select this tool.

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