Application Passwords auflisten

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

No annotations are provided, so the description carries the full burden. It clearly signals a read-only operation via 'Listet', but it does not disclose whether the output includes actual password values (vs. metadata), any permission requirements, or pagination behavior. For a simple list tool, this minimal transparency is adequate but not rich.

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, focused sentence that immediately states the action and scope. No filler or redundant text; it earns every word.

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 tool with one optional parameter and no output schema, the description covers the primary functionality adequately. Minor gap: it does not describe the return format (e.g., list of objects with fields), but for a simple listing tool this is not a major omission.

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 100% for the single optional userId parameter, and the schema already explains that it defaults to the current user. The description adds no additional parameter detail, so the baseline score of 3 applies.

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 uses the specific verb 'Listet' (lists) with a clear resource ('Application Passwords') and scope ('für einen Benutzer'). It unambiguously distinguishes this read-only listing tool from sibling create/delete tools like admin_create_app_password and admin_delete_app_password.

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 (to list app passwords for a user) but does not explicitly state exclusions or direct alternatives. Given the sibling tools for creating/deleting app passwords, some guidance on when to choose listing over those would be helpful, but the purpose is clear enough for basic selection.

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