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

Annotations already carry the read-only, idempotent, closed-world, non-destructive profile, and the description adds real value on top: newest-first ordering and the exact shape of each row (action type, acting user id/name/image, metadata, timestamp). No output schema exists, so this return-shape disclosure matters. Pagination behavior beyond the limit parameter is not covered.

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 short sentences; the operation and ordering lead, then row contents, then the use case. No filler, though the parenthetical example adds marginal cost for the guidance it delivers.

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 read-only list tool with no output schema and only two parameters, the description covers purpose, ordering, and record fields — enough to call it correctly. Gaps are minor: no pagination/cursor note and no differentiation from the other activity/comment list tools.

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 50%: storyId is documented as accepting a ticket key like 'ORB-526' or a UUID, while limit is documented only by its default/min/max constraints. The description mentions no parameters at all, so it adds nothing beyond the schema — baseline 3 fits for a 2-parameter tool whose schema does most of the work.

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 ('List the activity feed for a story') plus the ordering guarantee (newest-first). It does not name the near-siblings stride.list_recent_activity or stride.list_comments, so an agent must infer the boundary, but the core operation is unambiguous.

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?

It offers a motivating scenario ('useful before deciding whether to act on a story... has someone already commented?'), which implies when to call it. However, that example actually points at stride.list_comments, and no when-not or alternative-selection guidance is given for list_recent_activity or list_comments.

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