get_material_consumption_history

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

The description explains the aggregation and conversion behavior but does not disclose the output format or handle edge cases (e.g., no completed prints). With no annotations, the description should provide more detail on return structure and limitations.

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?

Extremely concise with front-loaded purpose. Two sentences plus a parameter line efficiently convey the tool's functionality without any extraneous text.

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 and no output schema, the description is mostly complete. It covers the main operation, aggregation logic, and parameter semantics. However, describing the return format would enhance 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?

The single parameter 'days' is well-described as a lookback window with a default of 30. This adds meaning beyond the schema's type and default, clarifying its purpose and usage.

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 it retrieves material consumption history from completed prints, aggregates per material type, and converts filament length to grams. This is specific and distinct from siblings like 'forecast_material_consumption' or 'get_material'.

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 versus alternatives like 'forecast_material_consumption'. While the purpose is clear, the description lacks explicit context for selection, leaving the agent to infer usage.

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