List Activity Kudoers

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

Annotations already declare read-only, idempotent, open-world behavior, so the description's real contribution is the cache-refresh caveat: an upstream refresh traverses all pages regardless of per_page. That is genuinely useful latency/cost context not present in structured fields. It still says nothing about auth or return shape.

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?

Two short sentences, front-loaded with the action and followed by the one non-obvious caveat. Every sentence 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?

Adequate for a simple paged read, but with no output schema the description should at least hint at what a kudoer entry contains or how paging metadata is returned. Auth expectations and empty-result behavior are also unmentioned.

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%, so page, per_page, and activity_id are already documented with ranges and defaults. The description reinforces the page/per_page interaction with the refresh behavior but adds no new parameter-level detail beyond the 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?

States a specific verb and resource (page through stored kudoers), which is clearly distinguishable from siblings like strava_list_activity_comments or strava_get_activity. It doesn't explicitly say the kudoers belong to a specific activity, relying on the name and required activity_id to convey that.

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 usage (paging over a stored list) but gives no explicit when-to-use/when-not guidance and no alternatives. No sibling tool overlaps strongly, so the omission is tolerable, but an agent gets no routing help.

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