update_llm_provider

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

No annotations exist, so the description must disclose behavioral traits. It indicates a destructive write operation ('replaces completely'), but does not mention required permissions, side effects, rate limits, or what happens to related data. The presence of an output schema is not referenced.

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 sentence of 11 words, efficiently conveying the core action and required inputs. It is front-loaded with the main verb and resource.

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 2 parameters, no annotations, and an output schema, the description provides essential information (full replacement, required inputs) but lacks details about prerequisites (e.g., provider must exist), error handling, or payload format specifics. It is minimally adequate.

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 add meaning. It identifies provider_id and payload but only describes the payload as 'full JSON payload,' which is vague and does not clarify expected structure or constraints beyond the schema's additionalProperties: true.

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 the specific verb 'Replaces' and identifies the resource as 'LLM provider completely.' It clearly distinguishes itself from siblings like delete_llm_provider and get_llm_provider by indicating a full overwrite operation.

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 states to provide provider_id and full JSON payload, which is necessary but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_llm_provider to check current state or delete_llm_provider). No contraindications are mentioned.

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