checkvist_get_current_user

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

The annotations already declare readOnlyHint and idempotentHint, and the description's 'Get' is consistent with these. The description adds minimal extra behavioral context beyond the annotations, though 'authenticated user' clarifies the auth requirement. No contradictions; standard read-only behavior is implied.

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 one succinct sentence that conveys purpose and context without filler. Every word contributes meaning, making it highly concise and appropriately structured.

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?

The description is sufficient for a simple, no-parameter read-only operation, and the annotations provide safety context. However, since there is no output schema, the description could be slightly more explicit about the shape of the returned profile information, though this is a minor gap.

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 and the schema is fully covered. Per the rubric, the baseline for zero-parameter tools is 4. The description does not need to add parameter-level detail because there are none.

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 is clear and specific: it states exactly what the tool does ('Get profile information') and for which resource ('the authenticated user'). This distinguishes it from sibling tools, which all target checklists, tasks, or notes.

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 description provides clear context: use this tool when you need the authenticated user's profile information. No explicit exclusions or alternatives are needed since this is the only user-related tool among the siblings, making the usage context sufficiently clear.

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