cleanup_material_function

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

Fully discloses destructive behavior (deleting nodes) and classifies which nodes are removed. Includes a dry_run option for preview. With no annotations, description carries full burden and excels.

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?

Four sentences total: one for purpose, one listing deletions, one warning, one for parameter docs. No fluff, front-loaded, efficient.

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 cleanup tool with 2 parameters and no annotations, the description covers purpose, exact deletions, usage caution, and parameter details. Output schema exists but not needed for 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?

Despite 0% schema description coverage, the description includes an 'Args' section explaining dry_run and implying function_path. Adds meaning beyond the schema's property definitions.

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?

Clearly states the action 'Remove unconnected/orphaned nodes' and the target resource 'Material Function'. Lists specific node types deleted, distinguishing it from siblings like 'cleanup_material_graph'.

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?

Explicit warning 'Only call when the user explicitly asks to clean up.' Provides context for appropriate use, though does not explicitly name alternative for different graph types or situational alternatives.

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