Assign Account

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description adds the useful prerequisite that account ownership and service type must match. It does not disclose what happens on a mismatch (error vs. silent no-op), whether an existing assignment is replaced, or whether re-assigning is a no-op, which are the remaining behavioral questions for this mutation.

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?

Two sentences, zero filler, with the action stated first and the constraints immediately after. The parenthetical pointer to list_accounts is compact and useful rather than redundant.

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 two-parameter, non-destructive, idempotent tool with full schema coverage and no output schema, the description covers purpose, prerequisites, and where to get the IDs. The only material gap is outcome semantics — replacement of prior assignments and error behavior on service mismatch.

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 the baseline is 3, but the description adds a cross-parameter constraint not expressed anywhere in the schema: the account_id value must match the service of the component_id. That relational rule is genuine meaning beyond the structured 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 gives a specific verb and resource ('Assign a connected third-party account ... to a component of a flow') plus the reason for doing so ('so the component can authenticate against its service'). It names list_accounts as the source of accounts and get_flow in the schema, which separates it from discovery tools, though it never distinguishes itself from the close sibling get_flow_accounts.

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 states two concrete preconditions for a valid call: the account must belong to the authenticated user and must match the component's service. That is clear usage context, but there is no explicit when-not guidance, no mention of what to do if the component already has an account assigned, and no pointer to an alternative when the precondition fails.

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