list_ingested_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 largely fails it. It never states that this is a read-only operation, whether results are paginated, how results are shaped, or what happens when both brand and material_id are supplied. The 'Requires Kiln Business' entitlement note is the one genuinely useful disclosure.

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 first sentence is front-loaded and useful, but the middle paragraph describes what a paid Kiln Business tier 'would' do rather than what this tool does, and the upgrade URL is pure promotion. Two of four lines do not earn their place.

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?

With no output schema, no annotations, and placeholder-only parameter docs, the description should explain the return shape, the list-vs-single behavior, and the entitlement mechanics. It covers only the last of these, leaving an agent unable to predict what a call returns.

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 coverage is nominally 100%, but every parameter description is the placeholder 'Default: ""', so the schema conveys no semantics. The description only faintly implies that an identifier selects 'one full spec'; it never explains how brand, material_type, and material_id interact or whether they combine as filters.

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 opening line states a resource ('ingested-materials library') and two modes (browse vs. fetch one full spec), which is more than a tautology. But the verb 'browse' is vague, the mechanism for the 'fetch one full spec' mode is never tied to a parameter, and nothing distinguishes this from siblings like list_design_materials or list_materials. The remaining text is marketing rather than purpose.

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 guidance on when to choose this tool over the many material-listing siblings (list_materials, list_available_materials, list_supported_materials, get_material_design_profile). The only usage-adjacent statement is the entitlement 'Requires Kiln Business', which gates access but does not help an agent decide between tools.

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