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

With no annotations, the description must disclose operational behavior, but it fails to do so clearly. The cryptic 'CONCORDANT/signpost NEVER HOLDS' and 'Paul's 7-step method' are unexplained. There's no explicit statement that this is a read-only operation, no mention of return format, pagination, or edge cases.

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 dense sentence with poetic phrasing and ALL-CAPS emphasis. It packs in a lot but is somewhat rambling and could be restructured with the action first. The content is valuable, but readability suffers.

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?

Given no annotations, no output schema, and 0% schema descriptions, the description covers basic usage but leaves important gaps. It doesn't explain what the returned data looks like, what 'Paul's 7-step method' means, or what 'NEVER HOLDS' implies. This is adequate but not thorough.

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 covers 0% of parameter descriptions, so the description compensates by explaining each parameter's role: id fetches one seed, q searches, tradition filters. It doesn't provide formats or constraints, but it does give functional meaning to all three parameters.

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 defines the tool's purpose: it lists, searches, and filters 'seeds' — true fragments with specific attributes. It provides usage patterns (id, q, tradition, else lists all). However, it doesn't explicitly differentiate from sibling tools like 'search' or 'witnesses', so it's clear but not fully unique.

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 gives explicit instructions for each parameter ('Pass id for one seed, q to search, tradition to filter, else lists all'). This is clear context for when to use the tool, though it doesn't mention alternatives or when NOT to use it, so it doesn't reach a 5.

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