Get Password

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds valuable nuance beyond annotations: Hudu returns 404 identically for missing records and unrouted paths, and IDs are not guessable. This helps the agent reason about error handling. The 'Operation class: Read' line is redundant but harmless.

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 concise and well-structured: it states the action first, provides resource context, then gives usage guidance and a behavioral warning. Every sentence contributes value without padding.

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 tool with rich schema and annotations, the description covers the essential context: what the resource is, how to obtain the id, and how errors behave. The only gap is not describing the return value structure, but the title and purpose make it clear that it fetches a password record. Given the tool's simplicity, this is sufficiently complete.

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 schema has 100% coverage with clear descriptions for both parameters (id as numeric Hudu id, response_format with enum and default). The description does not add substantial meaning beyond the schema, though it reinforces 'numeric id.' This is acceptable given schema coverage, so a baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Fetch one password by its numeric id.' It clearly distinguishes from siblings like hudu_list_passwords (list all) and hudu_update_password (update) by focusing on a single fetch operation. The added context of what a password record is in Hudu further grounds the purpose.

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 explicitly instructs: 'Use hudu_list_passwords first if you only know a name — ids are not guessable.' This gives a clear when-to-use versus alternative guidance. It also warns about the 404 behavior, helping the agent interpret failures correctly.

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