calculate_print_resolution

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

With no annotations, the description must fully disclose behavior. It states that the tool calculates and returns {effective_dpi}, implying it is a pure read-only computation. However, it does not explicitly state that there are no side effects, nor does it mention any permissions, rate limits, or other behavioral details.

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 two sentences, front-loads the main purpose, and includes a useful pointer to related tools. Every word is necessary and there is no verbosity.

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 presence of an output schema, the description does not need to detail return values, but it lacks explanation of edge cases (e.g., insufficient resolution for desired print size) or how 'maximum print size' is determined. The description is terse but minimally adequate for a straightforward calculation 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add any new meaning beyond what the schema already provides for the parameters. The mention of 'maximum print size' is a concept but does not elaborate on how it relates to the parameters.

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 the verb 'calculate', the resource 'print DPI quality and maximum print size', and the input 'from image pixel dimensions'. It is specific and distinct from the many sibling tools, which are all calculators but none with the same focus.

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 provides a hint to see list_bundles for related 'photographie' calculators, but does not explicitly state when to use this tool versus alternatives or when not to use it. There is no mention of prerequisites or exclusions.

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