Medidas corporales

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

No annotations provided, so the description carries full burden. It discloses the tool reads user data but does not mention caching, privacy implications, or error scenarios (e.g., missing measurements). Adequate for a simple read but could add nuance.

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?

One sentence, no wasted words. Could be slightly more structured (e.g., explaining return format), but it's concise and front-loaded with the action and data.

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 no-parameter tool without output schema, the description adequately explains what is returned. Sibling tools don't overlap, so no missing context. A minor improvement would be noting any units or constraints.

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?

No parameters, so schema coverage is 100%. The description adds value by listing the returned fields (height, weight, max heart rate) beyond the empty schema. Baseline for zero params is 4, and this is met.

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 retrieves body measurements (height, weight, max heart rate). The verb 'Obtiene' (gets) and specific resource 'medidas corporales' make the purpose unambiguous. It distinguishes from sibling tools by focusing on a unique domain not covered by others.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, context, or when not to use it. With siblings like get_user_profile and get_workouts, an agent lacks decision criteria.

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