read_material

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

No annotations are provided, so the description carries the full burden. 'Read' implies a non-destructive operation, but beyond that, no behavioral traits are disclosed: no mention of return format, error behavior, side effects, or whether special permissions are needed. The phrase 'with PBR formatting' is ambiguous and could mislead.

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 short sentence, so it is concise and easy to parse. However, it is under-specified: it lacks meaningful details that would justify its brevity. It is not bloated, but it also does not earn its place by conveying critical information.

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 simple tool with one parameter, no annotations, and no output schema, the description is incomplete. It does not explain what 'PBR formatting' means, what output the user should expect, or how it differs from generic resource/materials reading. The param schema covers file path, but the tool's behavior and return value remain opaque.

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 for the single parameter 'path' is 100%, with a clear description of it as a path to a .tres material file. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a verb and resource ('Read material') which gives a basic sense of purpose. However, the qualifier 'with PBR formatting' is vague and does not distinguish it from sibling tools like read_resource or read_physics_material. It does not clarify what PBR formatting means or what specific material data is returned.

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 provides no guidance on when to use this tool versus alternatives such as read_resource or set_material_param. There is no mention of intended use cases, prerequisites, or exclusions.

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