get_convert_settings

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

No annotations provided, but the description discloses that the tool reads from a specific config file (~/.config/promptready/settings.json) and is machine-specific. It implies read-only behavior, which is appropriate for a 'get' operation. The information is accurate and helpful.

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 (two sentences) with no wasted words. It is front-loaded with the main purpose in the first sentence and provides additional details in the second. Excellent structure.

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 tool's simplicity (no parameters, output schema exists), the description is complete. It explains what the tool does, where the data comes from, how it relates to convert_pdf and set_convert_settings, and that it is machine-specific. No gaps remain.

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?

With zero parameters, the schema is empty and description coverage is 100%. The description explains that no parameters are needed, which is sufficient. Baseline for zero-param tools is 4, and the description adds context by stating it shows defaults for the machine.

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 'Show saved convert defaults', distinguishing from per-file options. It specifies the file location and that convert_pdf uses these defaults, making the tool's purpose unambiguous.

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 indicates when to use the tool (to see defaults) and notes that it is not for per-file options. It mentions set_convert_settings as the companion for changing defaults, providing context for alternatives. Sibling tools like login/get_credits are clearly unrelated, so no further differentiation needed.

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