get_diet_profile

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

No annotations are provided, so the description carries the behavioral transparency burden. It clearly indicates a read operation and lists the fields contained in the profile, but it does not mention authentication needs, behavior when no profile exists, or whether defaults are applied.

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 states the action, resource, and key contents without filler. Every word contributes meaning.

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?

For a zero-argument getter with no output schema, the field list provides enough understanding of the return content. It is slightly incomplete because it does not state what happens if no diet profile has been set or point to sibling operations for modifying the profile.

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 tool has zero parameters, so the baseline is 4. The parenthetical describes profile fields rather than invocation arguments, which is appropriate for a call with no inputs.

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 uses a specific verb and resource ('Get user diet profile') and immediately clarifies what the profile contains: TDEE inputs such as sex, DOB, height, activity, goal, and macro preset. This differentiates it from siblings like set_diet_profile (write operation) and get_nutrition_goals (goals retrieval).

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 verb 'Get' and the parenthetical about TDEE calculation inputs imply this is the retrieval tool for the user's diet profile settings. However, it does not explicitly contrast this tool with close siblings like set_diet_profile, get_diet_daily_summary, or get_nutrition_goals, leaving usage context implied rather than stated.

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