report

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

Annotations provide non-destructive and non-read-only hints. The description adds that the tool returns a JSON string, but lacks details on side effects, authentication needs, or whether 'print_report' actually sends to a printer.

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 structured with a clear intro, operation list, parameter details, and return information. It is fairly concise, though the Args section could be slightly more streamlined.

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 operations and parameters adequately given the presence of an output schema, but lacks examples or default values that would help an agent understand typical usage patterns.

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 coverage, the description includes an Args section that explains each parameter's purpose and how they relate to operations, significantly adding meaning beyond the raw schema names.

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 explicitly states the tool handles 'Report generation and template management in InvenTree' and lists three distinct operations, clearly differentiating it from sibling tools like 'label' or 'part'.

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 lists operations and gives brief guidance on when to use each, but does not explicitly compare to sibling tools or state when not to use this tool.

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