Update Org LLM Fallbacks

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the important behavioral detail that this is a full replacement (overwrite) rather than a merge or partial update. However, it does not disclose side effects, permission requirements, or validation behavior, leaving gaps beyond what annotations provide.

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, front-loaded sentence with no wasted words. It efficiently conveys the action, target, and input format while remaining easy to parse.

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?

With a single parameter, rich schema descriptions, and no output schema, the description plus schema fully covers the operation's essentials. The description is brief but sufficient for a straightforward replace operation. Minor deduction for not explicitly stating the entire chain is overwritten (though 'Replace' already implies this).

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%: the fallbacks array is described as 'Ordered list of fallback LLM entries', and each sub-property (priority, provider_id, model, credential_id) has a clear description. The tool description adds no additional parameter meaning beyond the redundant phrase 'given ordered list', so the baseline of 3 applies.

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 clearly states the action ('Replace') and the resource ('organization's LLM fallback chain'), distinguishing it from the sibling tool lyzr_get_org_llm_fallbacks and other update tools. The verb and object are specific and unambiguous.

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 description implies the tool is used when the organization's fallback chain needs to be replaced, but it does not explicitly state alternatives (e.g., get_org_llm_fallbacks for reading) or conditions for non-use. The guidance is implicit rather than explicit.

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