Connect Hevy account

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

The description reveals key behavioral details beyond the annotations: the key is never sent through the conversation, the link is one-time, and the prerequisite of Hevy Pro is disclosed. This adds substantial context that is not present in the annotations, which are minimal.

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 two sentences, front-loaded with the core action ('Start linking YOUR Hevy account') followed by essential details. Every clause adds value, including where to get the key, the browser requirement, and the subscription requirement. No waste.

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 fully explains the linking flow, including the return of a one-time link and the security aspect of not sending the key through the conversation. It covers prerequisites and steps, though it could additionally mention behavior if the account is already linked or error cases, but these are not critical for initial use.

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 has no parameters (schema coverage 100% by default), so the description does not need to explain parameters. With zero parameters, the baseline is 4, and the description appropriately avoids adding irrelevant parameter information.

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 clearly states the tool's purpose: 'Start linking YOUR Hevy account' and explains it returns a one-time link for pasting an API key. This specific verb+resource combination distinguishes it from sibling tools like hevy_disconnect, hevy_status, and the various getters.

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 guidance on how to use the tool: it tells the user where to find the API key (hevy.com/settings?developer), that it must be done in a browser, and that it requires a Hevy Pro subscription. It does not explicitly mention alternatives or when not to use it, but the context of linking an account is clearly implied in contrast to sibling tools.

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