Get Weight History (FatSecret)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the month-scoping behavior and that it returns 'your' history (scoped to authenticated user). It does not describe return fields or pagination, so with annotations covering the safety profile, 3 is appropriate.

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 (7 words) that directly states purpose and key constraint. It is well-front-loaded with no filler.

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 tool is simple with one optional parameter and no output schema. The description covers the purpose and parameter semantics, but does not explicitly state the response structure. Given low complexity and strong annotations, it is adequate but could be slightly more explicit.

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 schema has one parameter 'date' with no description (0% coverage). The description defines the parameter as the anchor date for a month of history, which is essential semantic information not present in the schema. This fully compensates for the lack of schema description.

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 states a clear action: it retrieves the user's weight history. It specifies a time scope ('for a month containing the given date'), which differentiates it from sibling tools like fatsecret_get_food_entries or fatsecret_get_profile.

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 it: when you need a month of weight history for a specific date. It does not explicitly name alternatives, but the context is unambiguous. No exclusions are given, so 4.

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