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

Annotations already declare the operation read-only, idempotent, open-world, and non-destructive. The description adds valuable behavioral context beyond annotations by stating the per-call price in USDC on Solana and the equivalent HTTPS endpoint, though it does not describe payment failure behavior or return format.

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 definition is front-loaded with the core purpose and examples, and most sentences add useful information. The bounds restatement ('n and k run from 1 to 10000') duplicates the schema, slightly reducing conciseness but not enough to undermine clarity.

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 two-parameter math function with no output schema, the description gives enough context to call it correctly: purpose, example results, bounds, price, and endpoint. The main gap is the lack of explicit sibling differentiation and an explicit statement of what the return value is (the surviving seat number).

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 description coverage is 0%, so the description must carry the burden, and it does explain n as the number of seats/people and k as the elimination step. The worked examples ('5 people and every 2nd leave seat 3') concretely map the parameters to the computation, though the description does not explicitly restate parameter names in a formal mapping.

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 identifies the tool as computing the surviving seat in the Josephus problem, with concrete examples that confirm the operation. It does not explicitly differentiate itself from the sibling tools josephus_first, josephus_k2, josephus_order, or josephus_place, so an agent must infer which variant to call.

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 the problem statement and examples, but there is no explicit guidance on when to choose this tool over its sibling Josephus variants. No when-not-to-use conditions or alternatives are named, leaving routing to inference.

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