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

Annotations declare destructiveHint=true (mutation covered), so the description's main added value is the disclosure that line items cannot be supplied here and must be added in Current RMS, plus the POST /opportunities endpoint. It does not say what the call returns or whether partial failures are possible, leaving meaningful behavioral gaps for a 22-param create.

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?

Three tightly packed sentences that front-load the create action and required parameter before the housekeeping notes. The trailing 'Current RMS: POST /opportunities.' is largely inert for an agent but costs little.

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 22-parameter mutation with no output schema, the description covers the required field and the critical line-items caveat, which is the most important workflow fact. It stops short of telling the agent what identifier comes back, which matters because line items are added separately and presumably need the new opportunity id.

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 100%, so every field including the state enum mapping is already documented in structured data. The description only restates the store_id/member_id/date trio and adds no format or constraint detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

Using a specific verb+resource ('Create an opportunity') and glossing the domain term ('a rental job'), it clearly separates this tool from siblings like current_rms_create_member or current_rms_create_activity. The Enquiry/Draft/Quotation states further pin down what is actually being created.

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?

It gives real prerequisites: store_id is required with a pointer to current_rms_list_stores, member_id identifies the customer, and starts_at/ends_at carry the job dates. However, it never states when to prefer this over current_rms_update_opportunity or how it relates to current_rms_get_opportunity, so routing guidance is only implied.

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