get_settings

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

With no annotations, the description must carry full disclosure. It only states the action and return value, but does not disclose any behavioral traits such as read-only nature, permission requirements, or side effects. This is minimal disclosure.

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 exceptionally concise, with a clear verb-first sentence and a minimal return note. It is appropriately front-loaded and contains no unnecessary words.

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 zero-parameter getter, the description is adequate, but it could benefit from clarifying what 'runtime settings' includes. The presence of an output schema mitigates the need to specify the return structure.

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 tool has zero parameters, so the schema already documents everything. The description doesn't need to add parameter semantics; per the rubric, the baseline for 0 params is 4.

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 identifies the action ('Get') and the resource ('Node-RED runtime settings'), which is specific enough to distinguish from sibling tools focused on flows and nodes. However, it lacks additional context about what the settings pertain to, making it slightly less than a 5.

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?

No guidance is provided for when to use this tool versus alternatives. The description simply states what it does without any contextual advice, exclusions, or conditions.

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