get_training_context

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

With no annotations, the description carries the behavioral disclosure burden. 'Cache-backed' usefully signals that data may not be live, and 'transparent 7-day comparisons' suggests a defined comparison window, but it does not clarify freshness, staleness limits, or what 'transparent' guarantees.

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 front-loaded sentence with no filler. 'Transparent' adds little rigor, but overall it is compact and readable.

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 description covers the core resource, temporal window, and cache behavior, and an output schema exists, so return format is not a gap. However, it leaves the date parameter's role and the distinction from many sibling get_* tools unexplained, making it only minimally complete.

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?

The schema has no descriptions for the optional 'date' parameter (0% coverage), and the description never mentions 'date' or explains how it anchors the 7-day window. The '7-day comparisons' phrasing provides only weak indirect context.

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 uses an explicit verb and identifies the resource: recovery, recent training, and 7-day comparisons. It is clear enough to distinguish from individual calls like get_recovery or get_recent_activities, though it does not name a sibling or define 'context' precisely.

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 phrase 'cache-backed' and '7-day comparisons' implies when the tool is appropriate, especially compared to live or single-day tools. However, there is no explicit when-to-use/when-not-to-use guidance or alternative routing among the many sibling get_* tools.

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