Marathon Scout

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuine context beyond that by enumerating returned content (all stored dates, next edition registration state and check timestamp, Boston-qualifier status) and explaining that go-links are stable redirects whose destination is named by official_url. It doesn't cover behavior on an unknown slug, which keeps it below a 5.

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?

A single front-loaded sentence that names the key, then the payload, then the link semantics — every clause carries information and nothing is repeated from the schema.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, including link behavior. The only missing piece for a single-parameter lookup is error handling for an invalid or unknown slug.

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 coverage is 100% with an inline example, so baseline is 3; the description adds provenance that the schema lacks, telling the agent the slug must come from search_races rather than be guessed.

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?

States a specific verb and resource ('One race by its Marathon Scout slug') and immediately ties it to the sibling that produces the slug (search_races), so an agent can tell it apart from the search tool without opening either schema.

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?

Implies the correct workflow by noting the slug comes 'from search_races' and that live-tracking links exist 'once confirmed', which sets expectations. It never states an explicit when-not-to-use or an alternative for fetching multiple races, keeping it short of a 5.

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

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: a result cap of 10 (20 with an API key), the fields returned (next race date, registration status, Marathon Scout guide URL), and date ordering when the query is empty. It does not explain pagination past the cap, empty-result behavior, or error handling.

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?

Three tight sentences with the purpose front-loaded, then capability, then return shape and the no-query ordering rule. Dense but every clause carries information; the parenthetical examples are long but functional.

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?

With no output schema, the description steps in to describe returned fields and the result cap, which is the main thing an agent needs. Remaining gaps (limit default when unspecified, behavior with zero matches, whether region requires country) are minor for a read-only, zero-required-parameter search.

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 coverage is 75%, and the description adds meaning the schema does not: it frames the free-text query as able to carry compound constraints ("a flat spring marathon in Ohio"), and enumerates the filter axes (name, city, region, country, distance, date window, Boston qualifier) so the agent can map intent to separate parameters rather than dumping everything into query.

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?

States a specific verb and resource ("Find races for a runner") plus the exact scope: marathons, half marathons and ultras worldwide, searchable by name, city, region, country, distance, date window or Boston-qualifier status. It is unmistakably a search tool, but never mentions the sibling get_race, so the boundary between searching and fetching a single race is left to inference.

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 quoted natural-language examples ("a flat spring marathon in Ohio", "halves near Denver in October") implicitly show how to shape a query, and the note that no text query yields date-ordered results gives a usable default. However there is no explicit when-to-use/when-not guidance and no pointer to get_race for detail lookups.

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