get_personal_records

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. 'Get' implies a read operation, but the description does not say whether the response is all-time personal records, how the records are computed, whether any permissions are needed, or what kind of data is returned. This is minimal disclosure for a tool with no annotation support.

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 sentence with no filler and front-loads the action. It is appropriately compact for a zero-parameter tool, though it sacrifices useful contextual information in favor of brevity.

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?

There is no output schema, no annotations, and the tool belongs to a large family of similar getter tools. The one-sentence description leaves too much implicit: the return shape, the meaning of personal records, the range of activities covered, and how this differs from get_max_metrics. A more descriptive sentence could easily resolve these gaps.

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 tool has zero parameters and schema description coverage is 100%, so there are no parameter semantics for the description to add. The description's lack of parameter detail is not a deficiency because the input schema already fully defines the empty parameter set.

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 clear verb and resource: 'Get the athlete's personal records.' However, it adds little beyond the tool name and does not define what constitutes a personal record, such as whether it covers all activity types or all-time bests. It also does not distinguish this tool from siblings like get_max_metrics or get_activity, leaving the agent to guess the exact scope.

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?

There is no guidance about when to use this tool versus alternatives. The description gives no context about whether it should be preferred for historical bests, individual activity record details, or summary metrics. An agent selecting among the many getter siblings receives no routing help.

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