set_convert_settings

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

With no annotations, the description carries full burden. It discloses that changes persist for future 'convert_pdf' calls and that only desired fields need be passed. It does not mention reversibility or error conditions, but the behavior is well-explained for a settings mutation.

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 concise and front-loaded with the main purpose. It includes an example and bullet-pointed arguments. Minor redundancy (e.g., 'persists for future' repeated) but overall well-structured.

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 adequately covers the tool's core function but does not mention the output schema (likely a status or updated settings), error scenarios, or prerequisites. For a settings tool with a simple interface, this is adequate but leaves some gaps.

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 adds meaningful semantics for each parameter: enumerates engine options, explains 'include_tables', 'include_images' as heavier, and 'remove_references' as stripping when supported. This compensates for the lack of schema descriptions.

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 'update' and the resource 'saved convert defaults', and distinguishes from sibling tools like 'convert_pdf' and 'get_convert_settings' by emphasizing it updates persisted settings.

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 clear usage guidance: 'Only pass fields you want to change' and an example of setting the engine once for future conversions. However, it does not explicitly state when not to use or mention alternatives like 'get_convert_settings' for reading.

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