List Material Design 3 documentation

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

Annotations already declare readOnlyHint: true and openWorldHint: true, so the agent knows this is a safe read operation. The description adds the word 'live,' hinting at dynamic content, but does not disclose pagination behavior (cursor, limit) or that results may change over time. No contradiction with 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 sentence that is concise and front-loaded with the key action. However, its brevity comes at the cost of omitting parameter details, which is a structural gap. It is not wasteful but incomplete.

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 are covered. However, with 4 parameters and no parameter guidance, the description does not fully equip the agent to use the tool effectively (e.g., how to narrow results by category or prefix). It covers the basic purpose but misses control mechanisms.

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 0% schema description coverage, the description carries the full burden but fails to explain any of the 4 parameters (limit, cursor, prefix, category). The agent lacks context for filtering (prefix, category) and pagination (limit, cursor). The description adds no value over the parameter names.

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 explicitly states it lists 'live Material Design 3 Foundations, Styles, and Components documents.' This clearly identifies the verb (list), resource (MD3 docs), and scope (three categories), distinguishing it from sibling tools like search_md3_docs (search) and read_md3_doc (read a specific doc).

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 does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no indication of prerequisites, when to prefer this over search_md3_docs or read_md3_doc, or any exclusions. The context is implied but not stated.

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