infomaniak_get_public_cloud_kubernetes_service

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows this is a safe read. The description adds no further behavioral context (e.g., return format, pagination, or any side effects). It does not contradict annotations, but provides no additional transparency beyond them.

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 that directly states the tool's function without unnecessary words. It is appropriately front-loaded and minimal.

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 3-parameter read operation, this description is incomplete. It lacks parameter semantics and explicit alternative guidance. While the output schema and annotations cover some context, the absence of any parameter explanation makes it hard for an agent to know what values to provide.

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?

The input schema has 3 required parameters (kaas_id, project_id, public_cloud_id) with no descriptions, and schema description coverage is 0%. The description does not explain what these IDs are, how they interrelate, or how to obtain them. This is a critical gap for tool invocation.

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 'Read one Public Cloud Kubernetes service' uses a specific verb (Read) and a clear resource (Public Cloud Kubernetes service). It distinguishes from sibling tools by implying a single get operation versus list (plural) or manage (mutating).

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 does not explicitly state when to use this tool versus alternatives like infomaniak_list_public_cloud_kubernetes_services or infomaniak_manage_public_cloud_kubernetes_service. Usage is only implied by the verb 'Read one', which suggests fetching a specific service, but no exclusions or alternative guidance is provided.

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