Get current Tracker user

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds the 'auth probe' framing, which usefully signals this is a cheap credential check with no side effects, but it says nothing about what happens on unauthenticated calls or what the response contains.

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?

A single clause with no padding, and the identifying information comes first. It is terse to the point of being a fragment, but every word carries weight for a zero-argument tool.

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?

With no output schema the description could say what user fields come back, which is the one real gap. For a trivial, parameterless identity call whose annotations carry the safety semantics, the description plus the 'auth probe' note 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 takes zero parameters and the schema is fully closed (additionalProperties: false), so there is nothing for the description to clarify. Baseline 4 for a no-parameter tool.

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 names a specific resource ('the authenticated Yandex Tracker user'), which an agent can distinguish from tracker_users_get (a user by identifier), forms_me_get and wiki_me_get (the same 'me' concept in other products). It is a noun phrase rather than an explicit verb, but the title supplies 'Get' and the resource is unambiguous.

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 parenthetical '(a safe auth probe)' implies a use case — validating credentials — but there is no explicit statement of when to prefer this over tracker_users_get or the other *_me_get siblings, and no when-not guidance. Usage is implied rather than stated.

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