get_me

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

With no annotations, the description carries the full burden. It does state this is a read-only retrieval of the current user and even enumerates returned fields. However, it says nothing about behavior when no user is authenticated, token validity, or error conditions—valuable context for a tool whose entire access depends on the session.

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?

One sentence, no filler, and the achievement framing ('get...profile') is front-loaded. Field preview follows close behind, and there is nothing extraneous to excise.

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, single-resource tool with no output schema, the description is nearly complete, and the parenthetical list provides minimal return data. It could be more precise about what 'book counts' includes, but an agent could already decide whether to call this tool and roughly expect the result shape.

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?

There are zero parameters, so there is no ambiguity in the input schema. The description compensates by embedding the identity context ('currently authenticated', which is the effective input for selecting which profile is returned). Baseline of 4 for a parameterless tool is appropriate.

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 verb 'get' names a specific resource—'the currently authenticated Hardcover user's profile'—with concrete fields (id, username, name, book counts). Reading the first clause makes it clear this is a self-profile lookup rather than a search or a lookup by arbitrary username, distinguishing it from get_user_by_username without any need to open 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?

The phrase 'currently authenticated' establishes the context: use this when the agent needs the signed-in user's identity rather than an arbitrary user. The contrast with sibling get_user_by_username is implicit but easy to infer, though the description does not explicitly state 'use X instead when the username is known or the user is not the authenticated one.'

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