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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's added value is enumerating what is returned (traits + owner), which matters since there is no output schema, but it offers nothing on auth, rate limits, or error behavior.

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?

A single compact sentence that front-loads the core purpose ('traits + current owner') followed by the returned fields. No filler, though the parenthetical morpheme codes (R/B/T/L) are unexplained shorthand.

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?

Since there is no output schema, the description usefully enumerates the returned fields, which is the key information an agent needs. Remaining gaps are minor: no note on what happens for an out-of-range or non-existent token id.

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?

With a single parameter and 100% schema description coverage ('token id (0-23 for the genesis)'), the schema does the documentation work. The description only gestures at 'one KOINE token' without adding format, range, or lookup semantics 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?

Names a specific resource (one KOINE token by id) and enumerates the returned traits: generation, morphemes, parent ids, seed, owner. It clearly reads as a single-item detail lookup versus the listing siblings, though it never names those siblings explicitly.

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?

Usage is implied by 'one piece in detail' against siblings like koine_list_genesis and koine_provenance, but there is no explicit when-to-use statement or routing to an alternative. An agent can infer the intended case but gets no exclusions or prerequisites.

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