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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety behavior is covered. The description adds useful output-format context (one card each with specific fields) and implies recency ordering, which goes beyond the structured data. It does not mention pagination or limit effects, but those are minor for a read-only listing.

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 core purpose ('newest yanks') and packs the key output detail into a parenthetical. There is no redundant wording or filler.

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 read-only listing tool with one parameter, the description plus annotations and schema provide enough to call it correctly. It specifies the output structure and the ordering, though it omits any usage boundary with sibling tools and does not clarify that limit controls how many cards are returned.

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 description never mentions the 'limit' parameter, and schema_description_coverage is 0%. Even though the schema fully constrains the parameter with default, minimum, and maximum, the description adds no semantic meaning or guidance about how the limit behaves in relation to the returned cards.

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 the tool returns the newest yanks in the library and specifies the card structure with rank-1 line, author, source type, and URL. It does not explicitly contrast itself with sibling tools like get_yank or search_lines, so it stops short of full differentiation.

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?

No guidance is provided about when to use this tool versus alternatives such as get_yank, search_lines, or get_lines_for_url. There are no conditions, exclusions, or hints about when this tool is preferred, leaving the agent to infer from the name alone.

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