groups_ai_providers_update_ai_provider

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

With no annotations, the description carries the full behavioral burden. It does disclose meaningful behavior in 'Replace (full update)' — signaling that omitted fields may be reset — but says nothing about auth requirements, reversibility, or failure modes for what is clearly a mutating call.

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 first sentence is well front-loaded, but it is followed by an extensive keyword-stuffed tail ('Keywords: ... mealie.') that adds no selection value and bloats the definition. Real information density is low relative to length.

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 annotations, no output schema, and fully undocumented parameters, the description is thin. The PUT/full-replacement semantics is a useful start, but parameters and behavioral prerequisites remain uncovered.

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 for the undocumented parameters, yet it explains none of them. It never mentions provider_id, the required body fields (name, model), or the optional apiKey/baseUrl/timeout/requestParams/requestHeaders, leaving the agent to infer everything from the raw schema.

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 clear verb+resource ('Update Ai Provider') and adds genuine precision with 'Replace (full update)', which distinguishes PUT-style full replacement from partial edits. The sibling set contains create/get/delete variants, but the description doesn't explicitly contrast against them, so it stops short of a 5.

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?

No when-to-use guidance, no prerequisites, and no routing against adjacent tools such as update_ai_provider_settings. The 'Replace (full update)' note hints at the semantics but does not tell an agent when to choose this over a partial-update alternative.

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