Get Delx Wellness Profile

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

The description adds value beyond annotations by specifying the exact file path, that it never contains tokens, the local-export connector nature, and that the profile contract is standard across Delx Wellness MCP. No contradiction with 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 efficiently written with no filler. It front-loads the core purpose and returns a list of contents, then adds security and contract context in later sentences. Every sentence earns its place.

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 read-only tool with one optional parameter and no output schema, the description covers the key aspects: what it reads, what it returns, and security properties. However, it could be more precise about the return format or fields, though the listed items provide adequate guidance.

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 only parameter (response_format) has an enum and default in the schema, but the description adds no extra meaning or guidance about it. With 0% schema description coverage, the description should compensate but does not, though the parameter is trivial.

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 verb 'read' and the resource 'Delx Wellness profile' from a specific file path. It lists the returned fields and distinguishes itself from sibling tools by emphasizing it is a read-only local export.

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 explains the read-only nature and that it contains no OAuth tokens or API secrets because it's a local-export with no cloud auth, which guides usage context. However, it does not explicitly compare to sibling tools or state when to use vs. alternatives.

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