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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Retrieve'. It adds the behavioral detail that the user is tied to the access token, which clarifies the scope of the tool. For a zero-parameter GET endpoint, this is sufficient transparency, though it doesn't discuss rate limits or permission prerequisites.

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 sentence plus an endpoint reference, with no unnecessary words. It is front-loaded with the core action and resource, making it easy for an agent to parse quickly.

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-only tool, the description fully explains what it does. It doesn't describe the return object, but the endpoint and resource imply a standard user object, and no output schema exists. The description is complete enough for an agent to select and invoke the tool correctly.

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 input schema is empty (100% schema description coverage), and the description correctly adds no parameter information. With zero parameters, the baseline is 4, and no further elaboration is needed.

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 uses the specific verb 'Retrieve' and clearly identifies the resource as 'the currently authenticated user (whom the access token belongs to)'. This distinguishes it from sibling get_* tools like harvest_get_client or harvest_get_company, which target different resources. The REST endpoint 'GET /users/me' further anchors its purpose.

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 clearly implies when to use this tool: whenever the agent needs the identity of the authenticated user. It does not explicitly mention alternatives or exclusions, but the context is unambiguous given the sibling tools. This earns a 4 rather than a 5 because there is no explicit when-not-to-use guidance.

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