Set goals

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

Adds important context about requiring explicit user intent and confirmation before saving, which is beyond the annotations (idempotent, non-destructive). No contradiction.

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?

Two well-structured sentences: purpose first, then usage patterns. No wasted words.

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?

Sufficiently complete given 10 parameters, nested object, and no output schema. Covers usage patterns and the critical explicit_intent guardrail, though success/error behavior is omitted.

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?

Explains the two ways to specify goals (daily object vs flat shortcuts) and the explicit_user_intent parameter, adding value beyond the high-coverage schema descriptions.

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 sets local calorie, macro, and hydration goals, and distinguishes it from siblings like nourish_get_goals by requiring explicit user intent.

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?

Provides usage patterns (daily object vs flat shortcuts) and the condition to pass explicit_user_intent=true after confirmation, but does not explicitly list when not to use or alternatives.

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