Goals (Withings)

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context, such as what data is returned, whether goals are current or historical, or any prerequisites. Thus it does not go beyond the annotations.

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, short phrase with no extraneous content. It is concise and front-loaded, though it could be slightly clearer as a full sentence.

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?

There is no output schema to clarify return values, and the description is too minimal to be complete. It does not explicitly state that the tool retrieves goals or describe the format of the goals (e.g., current, daily, units). Given the simple nature and strong annotations, more context would be expected.

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 zero parameters, so the base score is 4 per the guidelines. The description does not need to explain parameter meanings since there are no parameters to describe.

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 'Your step/sleep/weight goals' identifies the resource (goals for steps, sleep, and weight), which distinguishes it from sibling tools like withings_get_activity. However, it lacks a verb indicating the action (e.g., 'retrieve' or 'list'), making the purpose somewhat vague and relying on the tool name for clarity.

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?

There is no guidance on when to use this tool versus alternatives such as withings_get_activity or withings_get_sleep. The description simply states what the goals are, without explaining the use case or exclusions.

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