Get Training Preferences

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

With no annotations provided, the description carries the full burden and largely carries it well: it discloses the complete return payload and implies a read-only nature through 'Returns'. It does not cover edge-case behavior such as what happens when the profile is incomplete or not yet set up, but for a parameterless getter the content disclosure is the dominant behavioral trait and it is thoroughly covered.

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 sentences with the core purpose front-loaded and the usage directive placed second, where it reinforces the tool's role in a workflow. The first sentence is a dense run-on enumeration, but every listed field earns its place because there is no output schema to carry that 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?

For a low-complexity tool (no params, no output schema, no annotations), the description compensates well: the exhaustive field enumeration stands in for an output schema, and the usage guidance covers when to call it. Minor gaps remain — behavior on missing profiles, staleness/caching, and scope confirmation — but nothing that would prevent an agent from invoking it correctly.

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 and schema coverage is 100%, so there is nothing for the description to explain — the baseline of 4 applies. The phrase 'the user's' implicitly clarifies the tool targets the current authenticated user, which adds a small touch of meaning beyond the empty schema.

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?

Opens with a specific verb and resource ('Returns the user's full profile') and then enumerates the exact content in three well-bounded categories (training preferences, body/personal info, food preferences). This clearly differentiates it from sibling getters like get_workout_history, get_workout_templates, and get_exercise_history, which target narrower slices of data.

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?

Gives explicit, actionable timing guidance: 'Always check this before generating a workout AND before generating or adapting a nutrition plan' and cross-references save_nutrition_plan for the downstream workflow. It lacks an explicit when-not-to-use statement or named alternatives for non-generating scenarios, so it falls just short of a 5.

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