strava_read

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

With no annotations, the description carries the full burden; the verb 'Read' does convey a non-mutating operation and the enumeration of returned content is useful disclosure. However, it omits whether element numbering is stable across reads, whether the read requires a page to be open first (strava_open), and any cost or timeout behavior.

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 with the verb first and the returned content enumerated after the colon. No filler or redundancy.

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, zero-required-parameter read tool with no output schema, the description adequately covers what comes back and that a current page is the target. The one real gap is that the numbering scheme of buttons/links is left undefined even though sibling click/type tools almost certainly consume those numbers.

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 100% and the single 'element' parameter is documented inline as 'Read only inside this element', so the schema does the work. The description never mentions scoping to an element, adding nothing beyond the schema; baseline 3 applies.

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 ('Read the current Strava page') plus the payload returned (text, numbered buttons, links, fields), which makes it distinguishable from mutation siblings like strava_click and strava_type. It does not, however, explicitly contrast itself with strava_status or strava_guide, which are the closest ambiguous alternatives.

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?

Usage is only implied: 'the current page' suggests reading state before acting, and 'numbered buttons' hints that the indices feed strava_click/strava_type. There is no explicit statement of when to call this versus strava_status or strava_guide, and no exclusions or ordering advice.

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