users_get_current

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

Discloses caching for 10 minutes, which is a notable behavioral trait. Without annotations, it adequately covers the tool's read-only nature and output details. Minor gaps on error scenarios.

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, well-structured with a clear opening, bullet-point workflow tips, and common use cases. Every sentence contributes meaningfully.

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 get tool with no output schema, the description provides adequate information on return content (permissions, role, access levels) and caching. Lacks full field list but sufficient for typical use.

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?

No parameters, so the description correctly notes 'No parameters needed'. It adds value by explaining what the tool returns, compensating for the lack of schema parameters.

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 'Get information about the current authorized user' with a specific verb and resource. It distinguishes from sibling tools like 'users_get' by emphasizing the current user and API token association.

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?

Provides workflow tips and common use cases, including when to check permissions or verify the API token. Implicitly tells when to use vs other user tools, though lacks explicit exclusions.

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