Get Password Folder

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context: that folders can carry access restrictions affecting visibility, and that Hudu returns 404 identically for missing records and unrouted paths — these go beyond the annotation hints.

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 compact and well-structured: it opens with the core purpose, adds domain context, then gives usage guidance. Every sentence contributes, with no redundancy or filler.

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?

This is a simple fetch tool with strong annotations and complete parameter schema. The description covers purpose, usage, and key behavioral quirks (404 handling, access restrictions). It does not explicitly describe the return object, but the action 'Fetch one password folder' plus the response_format parameter make this sufficiently clear.

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 coverage is 100%, so the schema already documents both parameters. The description supplements this by explaining that ids are not guessable and recommending a lookup workflow, adding meaningful semantics to the id parameter beyond its schema type and description.

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 specific action ('Fetch one password folder by its numeric id') with a clear resource and identifier, distinguishing it from siblings like hudu_get_password (which fetches a credential, not a folder) and hudu_list_password_folders (which lists, not fetches).

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?

It explicitly instructs to use hudu_list_password_folders first when only a name is known, explains that ids are not guessable, and warns about the 404 behavior — providing clear when-to-use and alternative guidance.

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