list_materials

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement that the operation is read-only, no permission requirements, no pagination or ordering behavior. The only implicit signal is that results are scoped to a user, which is not elaborated.

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?

At four words it is certainly short, but it is a sentence fragment rather than a front-loaded specification. This is under-specification rather than economical writing; nothing in it earns priority because nothing substantive is stated.

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?

An output schema exists, so return values need not be explained, but with no annotations and an undocumented parameter the description leaves an agent without the information needed to call it confidently. For a simple list tool the bar is low, yet this does not clear it.

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% for the single user_id parameter, which has a default of 'default'. The description never mentions this parameter or explains what happens when it is omitted, so it fails to compensate for the coverage gap.

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 is a bare noun phrase, 'The user's stored materials,' which essentially restates the tool name list_materials without a verb or scope statement. It tells the agent the resource is materials but adds nothing about whether this enumerates all materials, a page of them, or a filtered subset, and does not distinguish it from siblings like list_tracks or list_question_types.

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?

There is no when-to-use guidance and no mention of alternatives such as add_material, remove_material, or list_tracks. The agent must infer from the name alone that this is a read-style enumeration tool, with no exclusions or prerequisites stated.

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