Get Shared Wellness Profile

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds specifics: never contains OAuth tokens, API keys, or biomarkers, and clarifies no impact on GPS redaction. Adds value 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?

Very concise (few sentences) with front-loaded purpose. Every sentence adds meaningful content; no redundancy.

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?

Given the tool's simplicity (1 optional param, no nested objects, no output schema), description covers essential context: what profile contains, security note, and limitation regarding GPS redaction. Minor omission of response_format parameter details.

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 coverage is 0% but parameter response_format is a simple enum with default, well-defined in schema. Description does not mention or add meaning to this parameter, missing opportunity to inform agents of available formats.

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?

Clearly states it reads the 'canonical Delx Wellness profile' and is 'Read-only'. Distinguishes from sibling tools like strava_profile_update, strava_get_athlete, etc.

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?

Provides context on what the profile contains (onboarding data only) and explicitly notes it does NOT affect Strava's GPS-redaction default, helping agents avoid misuse. No explicit when-not-to-use but sufficiently clear.

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