get_ai_provider_settings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a read of group settings. It doesn't state whether this is read-only, what it returns, whether it requires group-admin privileges, or what happens on missing settings. The 'read-only' keyword is buried in synonym spam rather than stated as a behavioral guarantee.

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 mostly a keyword dump: ~30 synonyms for 'get setting' and 'list settings' followed by route and group keywords. None of it is front-loadable information; the single useful token (the GET route) is buried after the redundancy. Every synonym sentence is waste.

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?

No output schema exists, so the description should hint at the return shape (a settings object for the group's AI provider configuration), but it says only 'List settings'. Combined with no annotations, no permissions note, and no sibling differentiation, an agent lacks what it needs to call this correctly among the many AI-provider and group tools.

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?

Parameter count is 0, and the schema is empty with additionalProperties:false. Baseline for zero parameters is 4; there is nothing for the description to disambiguate, and it does not mislead about inputs. The keyword soup doesn't help but doesn't hurt parameter semantics.

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 wraps the tool name in a title and then repeats 'List settings' plus a keyword soup. The only substantive content is 'GET /api/groups/ai-providers/settings', which gives a resource path but no meaningful statement of what the tool returns or why an agent would call it over siblings like groups_ai_providers_get_ai_provider. The 30+ 'Keywords:' synonyms are tautological restatements, which is exactly the tautology pattern.

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, when-not-to-use, or alternative tool is named. The sibling list contains groups_ai_providers_get_ai_provider, update_ai_provider_settings, and other AI-provider tools that an agent must distinguish from this one, and the description provides zero routing guidance. The keyword spam ('search', 'find', 'browse') actively implies capabilities that aren't relevant to a settings GET.

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