Get Recent Runs

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

The description discloses the tool is read-only (consistent with readOnlyHint=true) and returns newest runs. It adds that results are limited by the limit parameter. No contradictions. Could mention any additional behavioral traits like sorting or absence of filters, but for a simple read tool it's adequate.

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 consists of two concise sentences. The first sentence provides usage guidance, the second states the behavior. No unnecessary text; every sentence adds value.

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 the tool's simplicity (1 parameter, no output schema, readOnlyHint annotation), the description is fairly complete. It explains the resource, ordering, and limit. It does not describe the return format or whether it returns full activity details, but this is acceptable for a list endpoint with low 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?

The description mentions 'up to the requested limit,' clarifying that the limit parameter controls the maximum number of results. The schema has 0% description coverage, so the description partially compensates by giving meaning to the parameter, but it does not elaborate on the default (20) or min/max constraints (already in schema).

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 returns the newest Run activities up to a limit, specifying verb (returns), resource (Run activities), and scope (newest, limit). It distinguishes from siblings like getRecentActivities (likely all types) and getActivitiesByType (with type filter).

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 explicitly says 'Use for current training analysis without fetching unrelated sports,' providing clear context for when to use and what to avoid. It does not name specific alternatives but implies them through the exclusion of unrelated sports.

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