seerr_get_me

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

The readOnlyHint annotation already signals this is a safe read operation, and the description does not contradict it. No additional behavioral context (e.g., authentication requirements, response details) is provided, but for such a simple get operation, the annotation plus description is adequate.

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, direct phrase with no filler words. It immediately communicates the tool's purpose with maximum efficiency.

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 tool with no parameters, a readOnlyHint annotation, and an output schema, the description "Get logged-in user" is complete enough for an agent to select and invoke it correctly. It could be slightly more explicit about returning the current user's profile data, but the phrase is unambiguous and sufficient.

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 zero parameters, so the baseline of 4 applies. There is no parameter information needed, and the description does not need to add anything beyond what the empty schema already conveys.

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 "Get logged-in user" clearly states the action (get) and the specific resource (the currently authenticated user). It distinguishes from sibling tools like seerr_get_user, which implies fetching a user by ID, while this targets the session's 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?

No explicit when-to-use or alternatives are mentioned. However, the phrase "logged-in user" implies its purpose: use it when you need the current authenticated user's profile. It lacks clarity on when to prefer this over seerr_get_user, but the intent is reasonably inferred.

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