inspect_static_mesh_sections

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states it is read-only, never saves, modifies, or exports the mesh, and explains that polygon-group names preserve material-section identity. This is strong transparency for a simple read operation, though it omits error-handling details.

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 well-structured: it leads with the purpose, references a knowledge base, gives a concrete example, and then explains safety and output semantics. It is reasonably concise and front-loaded, though the behavioral paragraph could be trimmed without losing value.

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?

The description covers the core purpose, safety, and an example, and the output schema presumably documents return values. However, it fails to explain the parameters, which are undocumented in the schema. This incompleteness makes it adequate but not comprehensive for an agent to use all parameters correctly.

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 input schema has zero description coverage for its three parameters. The description does not explain the meaning of lod_index or max_sections, only providing an example with lod_index=0. This leaves the agent without adequate understanding of the parameters, which is a significant gap.

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 clearly states the verb ('Inspect'), the resource ('one static mesh'), and the specific objects ('original material and render sections'). It differentiates from sibling inspection tools by specifying exactly what is inspected and by noting it is read-only. The example reinforces the usage, making the purpose unambiguous.

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 clear context: it is a bounded read-only operation, only accepts project assets below /Game/, and never modifies or exports the mesh. This implies when to use (for inspection without side effects) but does not explicitly name alternatives or state when not to use it. It gives enough guidance for typical use cases.

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