clm_lean_card_command_upload_working_package_file

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

The description discloses useful behavioral traits beyond the annotations: the operation is queued/background, creates a temporary upload record, and notifies the uploading user. However, the annotations mark destructiveHint=true, and the description does not explain what destructive action occurs (e.g., replacing a previous upload record), leaving an important ambiguity for a mutation command.

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 one dense sentence but contains only relevant information: what is queued, what processing does, notification behavior, and the follow-up step. It is front-loaded with the core action and wastes no words, though its long clause chain could be split for readability.

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 covers the operation's purpose, async nature, and place in the workflow, and an output schema exists so return-value documentation is not required. However, it leaves SiteId unexplained and does not clarify the destructive side effect indicated by the annotation, so the overall picture is incomplete for safe invocation.

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 0%, so the description must compensate, but it only indirectly hints at FileId ('uploaded working-package Excel file') and SheetName ('selected sheet'). SiteId is not mentioned at all, and no parameter is explicitly mapped or explained. This is insufficient for an agent to confidently populate all three fields.

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 a specific verb ('Queues') and names the exact resource ('initial background processing of an uploaded working-package Excel file'), then expands with concrete steps: reading the selected sheet, parsing rows/columns into a temporary upload record, and notifying the user. It also differentiates this from later steps by mentioning 'in preparation for the header-mapping step,' which distinguishes it from sibling header-mapping tools.

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 phrase 'initial background processing' and 'in preparation for the header-mapping step' clearly place this tool at the start of the upload workflow. It does not explicitly name alternative tools or say when not to use it, but the workflow context is strong enough for an agent to infer it should be called before header mapping, not after.

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