get_confluence_user

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

No annotations provided, but description states 'Returns user profile information' which adequately describes expected behavior for a read-only tool. No mention of permissions or error handling, but acceptable for simple retrieval.

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?

Two concise sentences covering purpose, identifier types, return value, and usage hint. No redundancy or unnecessary 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?

No output schema, but description summarizes return as 'user profile information.' Tool is simple, and with sibling tools listed, agent can infer when to use. Slight lack of detail on profile fields but acceptable.

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 clear descriptions for each field. Description only adds that identifiers are unique, which is already implied. Does not add significant meaning beyond schema.

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?

Clear action verb 'Get details for a specific Confluence user' and specifies identifier types (username, account ID, email). Distinguishes from sibling 'find_confluence_users' by emphasizing 'when you are confident you can uniquely identify a user.'

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?

Explicit guidance in bold: 'Use this tool when you are confident you can uniquely identify a user.' Implies alternative for ambiguous searches but does not name sibling tool. Still strong contextual cue.

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