list_asset_passwords

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only implies a read-only operation. It does not mention pagination, filtering, or whether archived items are included, leaving significant ambiguity for a list tool.

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 concise sentence with no wasted words, which earns it a high score on efficiency. However, it is under-specified given the complexity of the tool, so it is not fully appropriate in size.

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 8 parameters, no annotations, and no output schema, the description is severely lacking. It provides no context about the list's scope, filtering options, pagination, or return format, making it inadequate for reliable tool invocation.

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 contains 8 parameters with zero description coverage, and the tool description offers no explanation of what each parameter does. The phrase 'Get a list of Passwords' adds no meaning to the schema fields, failing to compensate for the low schema coverage.

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 that it retrieves a list of Passwords, which gives a clear verb and resource, but it lacks the specificity of 'asset passwords' and does not distinguish itself from sibling list tools. It is not a pure tautology but is very close to restating the tool name.

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 guidance is provided on when to use this tool versus alternatives like list_password_folders or get_asset_password. There are no use-case descriptions, prerequisites, or exclusions, leaving the agent to guess the appropriate context.

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