redmine_current_user

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

No annotations are provided, so the description carries the full burden of explaining behavior. It only restates the endpoint; GET implies a read, but it does not mention that authentication is required, what kind of user object is returned, or how the 'include' parameter affects the response.

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 front-loaded sentence with no filler or repetition. It is appropriately terse for a simple tool, though it errs slightly toward under-specification rather than crisp completeness.

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 one-parameter read operation this could be enough, but with no annotations and no output schema, the agent has no explanation of the return value or the include parameter's effect. Given the large sibling set and lack of routing guidance, the description is only complete for an agent already familiar with Redmine's /users/current.json endpoint.

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 description coverage is 0%, and the description does not mention the optional 'include' parameter at all. The enum values in the schema give some hint, but the agent is left to infer what memberships, groups, api_key, and auth_source actually control.

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 identifies the resource ('Current user') and the exact endpoint ('GET /users/current.json'), making it clear this retrieves the authenticated user's own record. It does not explicitly contrast itself with the sibling redmine_user_get, but the special 'current' endpoint is specific enough to avoid most confusion.

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?

There is no guidance about when to use this tool versus redmine_user_get or redmine_users_list. The endpoint implies 'current user' usage, but the description never states that this is for the currently authenticated account or that other user lookup tools should be used for arbitrary user IDs.

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