mat_validate_material

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

No annotations are provided, so the description carries the full disclosure burden. It conveys an analytical, non-speculative check and documents the return contract in detail, but it doesn't explicitly state whether the material is modified, whether compilation is triggered, or how invalid paths are handled.

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 tool's purpose is front-loaded, and Args/Returns/Example are cleanly structured; the Blueprint-comparison sentences add selection context without much bloat. The return list is somewhat redundant given the output schema, but the description remains focused.

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 one-parameter validation tool with an output schema, it covers the parameter format, return fields, interpretation cues, and an example. The main missing piece is explicit side-effect/safety disclosure (e.g., read-only, no material mutation), which matters more because annotations are absent.

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?

The schema only declares material_path as a string with no description, so the Args section provides the needed semantics: 'Full asset path' plus the '/Game/Materials/M_DemoB' example. This fully compensates for the 0% schema coverage and gives the agent an actionable format.

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 opens with a specific verb ('Validate') and resource ('a Material'), and enumerates the validation dimensions (expression count, disconnects, health score). This clearly separates it from material creation/compile/connection tools in the sibling set, though it does not explicitly name a competing tool.

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?

It positions the tool as giving materials the same trust model as Blueprints and notes it is narrower and non-speculative, which is useful context for when a material health check is appropriate. However, it never explicitly states when not to use it or which sibling (e.g., mat_get_compile_diagnostics) to prefer for compile-only concerns.

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