cura_print_time

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

With no annotations, the description must disclose behavioral traits. It only states the core function without mentioning prerequisites (e.g., slice must have been performed), side effects, errors, or whether it is read-only. Minimal transparency for a simple retrieval tool.

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?

Single sentence, no redundancy, and front-loaded with key information. Every word earns its place.

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 zero parameters and an output schema (not shown), the description provides sufficient context for what the tool does. However, it could mention the need for a prior slice and units of measurement. Still, it is reasonably complete for a simple tool.

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?

No parameters in input schema, so baseline is 4. Description does not need to add parameter information. It indirectly sets context but adds no semantic overload.

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 the function: returns estimated print time and material after slicing in Cura. It uses a specific verb ('Retourne') and resource ('temps d'impression estimé + matière'), distinguishing it from sibling tools that perform slicing or other operations.

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?

Description implies usage after slicing ('après une découpe'), but does not explicitly state when to use this tool versus alternatives or provide conditions or exclusions. Sibling tools like cura_slice and slice suggest sequence, but no direct guidance.

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