mat_compile

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

With no annotations, the description carries the full burden. It does disclose the default save behavior and lists return fields. However, it promises 'a list of compile messages' in the opening, but the Returns section lists only booleans and counts, leaving ambiguity about what the structured result actually contains.

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?

Well-structured with sections for args, returns, KB pointer, and example; purpose is front-loaded. Slightly verbose, and the compile-messages inconsistency adds avoidable confusion, but every section earns its 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?

Covers purpose, when to use, parameters, return structure, and includes an example. It is incomplete because it never resolves the gap between the promised compile messages and the listed output fields, and the KB reference to blueprint fundamentals appears tangential for a material compile tool.

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 0%, but the description fully compensates by defining material_path with a full asset path and concrete example, and save_after_compile with its default and meaning. The example call further clarifies usage.

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?

States a specific verb and resource: 'Compile (recompile) a Material and return structured errors/warnings.' The purpose is clear, but it does not explicitly distinguish itself from closely related siblings like mat_get_compile_diagnostics or compile_material_and_report.

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?

Provides clear when-to-use context: 'Always run this after finishing material expression edits.' This is a concrete trigger. However, it does not mention alternatives or exclusions, such as when another diagnostics-focused tool would be more appropriate.

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