Nourish profile get

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds value by detailing what data is returned, but doesn't disclose additional behavioral traits like permissions or side effects. With annotations covering the safety aspects, a score of 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 two sentences, front-loading the core purpose and adding relevant details without extraneous words. Every sentence serves a clear purpose.

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 simple read-only tool with one optional parameter and no output schema, the description covers the essential purpose and data content. It does not explain the response_format parameter, but overall the context is sufficient for an agent to understand the tool's role, especially given sibling tools handle updates and other operations.

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 single parameter 'response_format' has an enum (json, markdown) but zero schema description coverage. The description does not mention this parameter or explain its effect on the output format. Since the description adds no meaning beyond the schema's enum values, and the schema lacks descriptions, the parameter semantics are poorly supported.

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 it returns the shared Delx Wellness profile, is read-only, and lists the specific data it surfaces (calorie/macro targets, dietary preferences, restrictions/allergies, goals). It also distinguishes itself by noting it's used by nourish coach/suggest tools, differentiating from sibling tools like nourish_profile_update.

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 indicates when to use the tool (to get profile data for personalization) and notes it's read-only, implying no modifications. It doesn't explicitly state alternatives, but the sibling 'nourish_profile_update' is the obvious counterpart for write operations. Overall clear usage context.

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