get_hill_score

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it retrieves hill score data between dates; it does not disclose whether the result is a daily series or a single aggregate, how boundary dates are handled, or any request constraints. This is a meaningful gap for a date-range data query 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?

The description is concise and front-loaded with the core purpose. The Args block is minimal and adds the useful format detail without unnecessary fluff. It is slightly formulaic but earns its place.

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 two-parameter date-range tool with an output schema available, the description is minimally adequate. However, the absence of annotations and lack of behavioral detail around date handling mean an agent is left to infer important execution semantics. It is complete enough for a straightforward getter but not rich enough for confident invocation.

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 description coverage is 0%, so the description must compensate. It does add value by specifying the YYYY-MM-DD format for both parameters, which the schema omits. However, it does not clarify ordering, inclusivity, or the meaning of 'hill score data' beyond the parameter names.

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 states a specific verb and resource: 'Get hill score data between dates'. This is clear and distinct from most siblings, though it does not explicitly differentiate itself from other score/trend tools like get_endurance_score or get_progress_summary_between_dates.

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 usage when a hill score is needed over a date range, but it provides no explicit guidance on when to choose this tool over alternatives or any exclusions. There is no mention of prerequisites, date inclusivity, or related sibling tools.

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