get_daily_resilience

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, or rate limits. It only states what the tool returns, lacking transparency beyond the basic function.

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 extremely concise with one sentence for purpose and a clean args list. No superfluous text, and the purpose is front-loaded, allowing quick understanding.

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 simple getter with only two optional parameters and an output schema, the description is sufficient. It explains the return type ('resilience data indicating recovery capacity and stress tolerance') and parameter behavior. However, it could mention that the output schema details the data structure.

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?

Despite 0% schema description coverage, the description adds valuable context: it specifies the date format ('YYYY-MM-DD') and default values ('yesterday' and 'today'), which are not present in the schema (which has defaults of null). This compensates for the lack of schema documentation.

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's function: 'Get resilience data indicating recovery capacity and stress tolerance.' It uses a specific verb ('Get') and resource ('resilience data'), and the purpose distinguishes it from sibling tools like 'get_daily_activity' or 'get_daily_sleep'.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., 'get_daily_readiness' or 'get_daily_stress'). No when-to-use, when-not-to-use, or prerequisite information is given.

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