infomaniak_get_database_user

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

Annotations already declare readOnlyHint and idempotentHint, making the safe read nature clear. The description adds valuable context about what the detail includes (applications, permissions, link to phpMyAdmin), going beyond the annotations. It does not contradict annotations.

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?

A single sentence that is concise, front-loaded with the verb 'Fetch', and contains no filler. Every word adds value.

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 read-only get tool, the description provides sufficient context: what the tool returns and the resource type. Output schema covers return structure, and annotations cover safety. The only minor gap is the lack of parameter details, but that is a separate dimension and not critical for overall 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 covers 50% of parameters (user_name has a description, hosting_id does not). The description does not compensate for the undocumented hosting_id; it only mentions 'single MariaDB-level user' which implicitly relates to user_name but not to hosting_id. No additional parameter meaning is provided beyond the 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?

The description clearly states the action ('Fetch') and the resource ('detail of a single MariaDB-level user'), and specifies the type of details returned ('applications, permissions, link to phpMyAdmin'). It distinguishes from siblings by emphasizing 'single' user as opposed to listing tools like infomaniak_list_database_users.

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 implies when to use this tool: when you need details of a single MariaDB-level user. It does not explicitly mention alternatives or exclusions, but the 'single' scope provides clear context relative to list tools. No misleading guidance.

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