get_profile

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

With no annotations provided, the description carries the burden. 'From cache or API' discloses a caching/fallback behavior, but lacks details on privacy, error handling, or data freshness. This is minimal behavioral transparency, adequate for a read-only profile fetch but not enriched.

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 a single concise sentence, front-loaded with the main action and resource, and includes only essential details (fields and source). No wasted words.

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?

The tool is simple (no params, no side effects, no complex behaviors). The output schema covers return values, and the description adds the cache/API sourcing context. This is complete for the tool's complexity level, especially compared to siblings which are more specialized.

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?

There are zero parameters, so schema coverage is trivially 100%. The description adds no parameter-specific info because none exist, but it does list the returned fields in parentheses, which helps the agent know what the profile contains. Baseline 4 is appropriate for a no-parameter tool.

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 'Return user profile' with specific fields (birth_date, height_cm, sex), distinguishing it from sibling tools that focus on body composition or measurements. The verb 'Return' and resource 'user profile' are specific and unambiguous.

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 implies this tool is for fetching profile data as opposed to sibling tools (which handle body composition/measurements). However, there is no explicit 'when to use this vs alternatives' guidance, only the source note 'from cache or API' which gives context but not exclusions.

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