groups_ai_providers_get_ai_provider

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

No annotations are provided, so the description carries the full disclosure burden. A GET endpoint implies a read, and the keyword list weakly signals 'read-only', but the description never states authentication requirements, error behavior for an unknown provider_id, or what is returned. For a no-annotation tool this is thin.

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 meaningful content is one short clause ('Get provider' plus the endpoint path); the rest is a very long keyword-stuffing tail that repeats synonyms and inventory terms. This is bloat, not concision, and pushes the useful signal to the front only barely.

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 simple one-parameter GET with no output schema and no annotations, an agent still needs to know the param's origin and the auth/read semantics. The description supplies the endpoint but omits these, and the keyword list substitutes volume for completeness.

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% for the single provider_id parameter. The path template {provider_id} hints that it is a URL path segment, and the schema's uuid4 format is the only real guidance, but the description adds no meaning about where to obtain the ID or what it identifies.

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 states a verb (get) and resource (AI Provider) and even exposes the raw endpoint path, which pins down the resource precisely. However, "Get provider" is largely a tautological restatement of the tool name and title, and there is no differentiation from siblings like get_ai_provider_settings or groups_ai_providers_update_ai_provider beyond the namespace prefix.

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?

There is no statement of when to use this tool versus alternatives such as get_ai_provider_settings, create/update/delete AI provider, or whether it requires an ID obtained elsewhere. Usage context is only implied by the name and path.

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