Get current Forms 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. The description adds the additive detail that this doubles as an auth probe (no side effects, useful to validate a session), but says nothing about what identity fields are returned or any auth failure behavior.

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 short sentence with the resource and the probe hint front-loaded and zero filler. It reads as a label fragment rather than a crafted sentence, but nothing needs trimming.

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 no-argument identity read with full annotation coverage and no output schema, the description is essentially sufficient. It could be marginally stronger by noting the returns are the current user's identity fields, but no critical information is missing.

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?

Zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate and it makes no misleading parameter claims.

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 a specific resource — the authenticated Yandex Forms user — and the title supplies the verb ('Get'), so an agent can tell it apart from survey/question/answer siblings. It never states the verb in the description body itself, leaving it as a noun fragment rather than a full verb+resource statement.

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?

Calling it 'a safe auth probe' implies a usage scenario (verifying credentials/permissions before other Forms calls), which is genuinely helpful. However, no explicit when-to-use/when-not criteria or alternatives are named, and it doesn't distinguish itself from the analogous wiki_me_get or tracker_me_get beyond the product prefix.

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