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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds meaningful context beyond that: the result is scoped to the credential identity rather than a query parameter, and it maps to GET /v1/users/me, which confirms no state change and no side effects. It stops short of describing the returned payload's shape or failure modes (e.g. invalid key).

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?

Two sentences, zero waste, with the core purpose front-loaded and the REST mapping relegated to supporting detail. Nothing needs to be trimmed.

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 parameterless read tool with no output schema and readOnlyHint already set, the description supplies enough to call it correctly and interpret the result as 'the caller's own user record'. A brief note on the returned user object or the error condition for an invalid key would make it fully complete.

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, so per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent parameter semantics.

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?

States a specific verb and resource ('Get the user') and pins the scope with 'associated with the current Folk API key', which cleanly separates it from folk_get_person and folk_list_users. It even names the underlying REST route (GET /v1/users/me). An agent can identify the tool's identity semantics without opening the schema.

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?

Usage is implied rather than stated: 'current Folk API key' tells the agent this is a self-identity lookup rather than a lookup of an arbitrary user, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. folk_list_users for enumerating users). Minimum viable but leaves routing to inference.

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