Nourish profile get

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds value by specifying the exact file location (~/.delx-wellness/profile.json) and listing the data categories (calorie/macro targets, dietary preferences, etc.), which is additional context beyond annotations.

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 primary action and then listing the contents. Every sentence serves a purpose with no unnecessary words, achieving excellent conciseness.

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 tool with no output schema, the description covers the key output categories. It does not mention the response format (JSON/markdown) controlled by the parameter, but that is documented in the schema. Overall, it is sufficiently complete for the tool's simplicity.

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?

Schema description coverage is 50%, and the description does not directly explain the parameters. However, the 'privacy_mode' parameter has a detailed description in the schema, and the tool description clarifies the overall content of the profile, which indirectly aids understanding. No parameter info is added in the description itself.

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 returns the shared Delx Wellness profile and specifies its contents (calorie/macro targets, dietary preferences, etc.). The verb 'Returns' combined with the resource makes the purpose unambiguous, and it is distinct 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 the tool is read-only and intended for personalization by coach/suggest tools, implying when to use it. It does not explicitly state when not to use it or mention alternatives, but the sibling context (e.g., nourish_profile_update) provides differentiation.

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