rhino_document_settings

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

The description aligns with readOnlyHint=true, indicating no mutation, and adds useful context about which settings are covered. It does not add deeper behavioral detail such as document targeting or output shape, but the annotation and output schema reduce the need for that here.

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 a single compact phrase with no filler and the key content is front-loaded. It could be marginally improved by using a proper verb such as 'Returns', but it is efficiently worded for an agent to parse quickly.

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?

For a simple read-only settings summary with one documented parameter and an output schema, the description is largely sufficient: it names the settings bundled and the annotation clarifies side effects. The main missing element is explicit guidance on when to choose this over individual getter tools.

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?

The description does not mention doc_id, but the schema documents it clearly with the default value 'active' and an explanation of its meaning. Since there is only one simple parameter, the description adds little beyond the schema, but no significant gap exists.

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 identifies the resource as document settings and states the contents: units, tolerances, and base point, bundled into one call. It lacks an explicit verb like 'returns' or 'gets', but the readOnlyHint and 'Document Settings Summary' title clarify that it is a read-oriented summary rather than a mutation tool.

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 phrase 'in one call' implies this tool consolidates what separate unit, tolerance, and base-point tools might do individually. However, it does not explicitly name alternatives such as rhino_document_units_get, rhino_tolerance_get, or rhino_origin_set, nor does it state when this combined call should be preferred over those.

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