get_resilience

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

No annotations are provided, so the description carries the full burden. It indicates a read operation with no destructive impact. However, it does not disclose behaviors like data availability for missing dates, defaulting behavior (though schema mentions 'defaults to today'), or any rate limits. Minimal but adequate for a simple data retrieval tool.

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?

Two sentences with no wasted words. The first sentence states the purpose and key inclusions; the second adds value by describing the resilience level scale. Well-structured and front-loaded.

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 two simple optional parameters, no output schema, and no nested objects, the description is fairly complete. It explains what the scores include and the range. A minor gap is not specifying that results are returned as daily data, but overall sufficient for a tool of this complexity.

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 100%, and the description does not add extra meaning beyond what the schema provides. It mentions 'daily' and date range implicitly but does not explain parameter semantics further. Baseline score of 3 is appropriate.

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 'daily resilience scores' and explains what they measure (sleep recovery, daytime recovery, stress contributors) and the range (limited to exceptional). This verb+resource combination is specific and distinguishes it from related sibling tools like 'get_readiness' or 'get_stress'.

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 is provided on when to use this tool versus alternatives. Sibling tools include 'get_readiness', 'get_stress', and other resilience-related analytics, but the description does not help the agent decide which to pick.

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