get_confluence_current_user

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

The description clearly states the return fields and implies a read-only operation, but with no annotations, it could explicitly mention that the tool is non-destructive and requires no special permissions. Adequate for a simple retrieval 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 consists of two concise sentences with no filler. Every sentence adds value by identifying the action and the output fields.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is complete. It specifies the purpose and return fields, which is sufficient for correct 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 tool has 0 parameters and schema description coverage is 100%. The description does not need to add parameter-level details beyond what the schema provides. The baseline for 0 parameters is 4.

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 action ('Get details') and the resource ('authenticated Confluence user'), and lists specific return fields (account ID, display name, email, profile picture). The tool name is self-explanatory, and the description distinguishes it from siblings like get_confluence_user and get_jira_current_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?

The description implies usage context (retrieve current user info) but does not explicitly state when to use it vs alternatives like get_confluence_user or get_jira_current_user. No when-not-to-use guidance is provided.

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