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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, while the description redundantly repeats 'Read-only.' It does add useful return-content context by naming the shared analysis fields and embeddability flag, but it does not describe not-found behavior, permission/sharing constraints, or other operational traits beyond the annotations.

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 compact sentence that front-loads the resource and lists the returned fields efficiently. 'Read-only' is a minor redundancy because the annotations already declare readOnlyHint=true, but there is no significant wasted wording.

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 one-parameter read tool with annotations covering safety, the description adequately identifies what is returned. However, it omits parameter meaning and not-found or access behavior, leaving gaps that matter for correct invocation even at this low complexity.

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%, and the description never mentions material_id, its requiredness, or that it must be an integer of at least 1. The input schema supplies the type and requirement mechanically but no semantic description, so the description does not compensate for the low coverage.

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 states a specific resource and its contents: 'One material with its shared analysis: level, topic, summary, how many vocabulary units it teaches, and whether its player can be embedded.' The singular 'One material' helps distinguish it from list-style siblings, though the retrieval verb is implied by the tool name rather than stated 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?

The description gives no explicit when-to-use guidance, no when-not-to-use guidance, and does not name alternatives such as language_list_materials for discovering a material ID. Usage is only implied by the singular resource reference and the read-only note.

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