get_password

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

The description warns that the tool includes the actual password value, indicating sensitive data exposure. However, with no annotations provided, it does not disclose security or permission requirements, rate limits, or logging behavior, leaving gaps in transparency.

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, clear sentence of 18 words, front-loading the core purpose and key detail about password retrieval. No wasted words.

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?

Without an output schema, the description does not detail return fields beyond mentioning the password value. For a retrieval tool, this is somewhat incomplete. It lacks description of read- only semantics or any caveats.

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% with both 'id' and 'show_password' described. The description adds minimal value beyond the schema, only hinting at the password value inclusion. Baseline score of 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 clearly states the tool gets a password entry by ID from IT Glue and includes the actual password value. It uses specific verb 'get' and resource 'password entry', distinguishing it from sibling tools like search_passwords which search rather than retrieve by ID.

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 usage when you have a specific password ID, but does not provide explicit guidance on when to use this tool versus alternatives like search_passwords, nor does it mention any prerequisites or restrictions.

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