get_blueprint_material_info

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

Description implies a read-only operation, but with no annotations provided, it lacks details like error handling (e.g., blueprint not found) or whether any side effects occur. Adequate for a simple getter but lacks depth.

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?

A single, concise sentence that is front-loaded with the action and resource. No redundant 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?

Given the tool's low complexity and existence of an output schema, the description is minimally adequate. However, it could mention what the returned info includes (e.g., slot names, materials) to improve completeness.

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?

Only parameter 'blueprint_name' is mentioned but not elaborated. Schema coverage is 0%, so description should add meaning like format or valid values, but it does not. The parameter's purpose is inferred from the tool name, but explicit guidance is missing.

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?

Description clearly states it retrieves material slot info for Blueprint mesh components. The verb 'get' and resource 'blueprint_material_info' are specific, and it distinguishes from sibling tools like get_material_info (general) and get_actor_material_info (actor-specific).

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?

No guidance on when to use this tool vs alternatives. Does not mention prerequisites, such as whether the blueprint must be loaded, or when to use other material-related tools.

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