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

With no annotations, the description carries the burden of behavioral disclosure. It uses 'fetch', implying a read operation, and explains how to extract the id from a link. However, it does not mention error handling, permissions, rate limits, or whether the response includes the full slip or only picks.

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 is a single sentence that front-loads the primary action ('Fetch a slip by id') and adds supporting detail without excess. Every clause contributes to either purpose or parameter semantics.

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 one-parameter tool without an output schema, the description mentions that it lists picks, giving some return context. However, it does not clarify whether the response includes slip metadata, how errors are returned, or pagination behavior. Given the low complexity, this is adequate but has gaps.

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 input schema only defines id as a string with length constraints, with 0% description coverage. The description adds essential semantic meaning: 'the part after /slip/ in a squadride.app link'. This directly helps an agent construct a valid id, which is exactly what a schema cannot convey.

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 a specific verb and resource: 'Fetch a slip by id' and 'list its picks'. This distinguishes it from siblings list_books and translate_bets, which are about different domain objects. The id extraction hint further clarifies the tool's scope.

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 provides no guidance on when to use this tool versus alternatives, and no prerequisites or exclusions. The only usage-related detail is how to derive the id from a link, which is more parameter semantics than tool selection guidance.

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