By Question

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the key behavioral trait 'Deterministic', which is not covered by annotations. However, it omits details about the output format (e.g., whether it returns a hexagram text, lines, or binary), which is a gap given no output schema exists.

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 extremely concise with two sentences plus a group tag and example. The first sentence immediately states the core purpose. Every element is functional with no wasted words.

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 the tool's simplicity (one parameter, deterministic), the description is mostly adequate but lacks clarity on the return value. With no output schema, it should at least mention the structure of a hexagram or what the response contains. The group tag helps organizational context but does not compensate for missing behavioral details.

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 schema defines one required parameter 'question' with type and length constraints but no description (0% coverage). The description provides an example request body {"question":"..."} which clarifies the parameter name and JSON format, but adds no additional meaning about the question's purpose or constraints beyond the schema. This is adequate but not exceptional.

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 'Deterministic hexagram from question text', specifying the verb (generates), the resource (hexagram), and the input (question text). It distinguishes itself from siblings like iching_throw_coins (random) and iching_with_changing_lines by highlighting determinism, and the group tag 'I Ching (Standalone)' further clarifies 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 implies usage for deterministic readings via the term 'Deterministic', but does not explicitly state when to use this tool versus alternatives like iching_throw_coins (random) or iching_daily. No exclusions or context are provided, leaving the agent to infer intent from the tool name and description alone.

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