get_client_profile

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

The description aligns with the readOnlyHint annotation by indicating a read operation. It adds value by specifying the returned computed metrics, but it does not disclose any other behavioral details (e.g., error handling, authorization requirements).

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, front-loaded sentence that efficiently conveys the action, resource, computed metrics, and necessary parameter. There is no extraneous information.

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?

Given the lack of an output schema, the description only vaguely indicates the return value ('fitness profile + computed metrics'). It does not specify the structure of the profile or the exact computed metrics, leaving some ambiguity for the agent.

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?

With 0% schema description coverage, the description compensates by clarifying that the userId parameter refers to the client's user ID, adding semantic meaning beyond the bare schema. It does not elaborate on format or validation, but the single required parameter is well-addressed.

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 action ('Get') and the resource ('client's fitness profile + computed metrics'), with specific mention of BMI, TDEE, and recommended calories. It effectively distinguishes from sibling tools like calc_tdee which only compute a single metric.

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 a clear parameter instruction ('Pass the client's user _id') but does not offer comparative guidance on when to use this tool versus alternatives (e.g., calc_tdee, calc_1rm) or mention prerequisites or exclusions.

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