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

Annotations only give the generic readOnly=false/destructive=false/openWorld=false profile, so the description must add context and it does: it discloses the auth scope requirement and the underlying Classic reconcile behavior being reused. It stops short of saying what the call mutates on the transaction beyond the account pick, or whether it is idempotent.

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 short sentences, front-loaded with the action and the endpoint it maps to, with the required scope last. Only mild jargon ('Websome', 'Classic') adds friction, but nothing is wasted.

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 precondition and permission but says nothing about the result of a successful apply (e.g. what is updated on the transaction or what response to expect). Adequate but leaves a real gap.

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 parameters are fully documented in structured fields and the description only reinforces the source of accountId. It adds no syntax or constraint detail beyond what the schema already provides, which is the baseline expectation here.

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 precise verb+resource: applying a cashcoding account recommendation to a transaction, and names the exact endpoint semantics it mirrors ('Classic cashcoding reconcile endpoint as the Websome transaction page'). This clearly separates it from the read-only sibling list-transaction-cashcoding-recommendations.

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?

Explicitly instructs the agent to pass an accountId obtained from list-transaction-cashcoding-recommendations and states the required permission scope (company:documents:write), which is a real prerequisite. It does not state when not to use it or what happens if the transaction already has an account.

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