get_render_settings

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

With no annotations, the description discloses important behaviors: returning only existing and data-safe parms, rejecting script/callback/command/executable types, and applying a response cap. This adds meaningful context beyond a simple read operation.

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 compact, using code formatting and a reference to design.md, with no extraneous words. Every sentence adds specific behavioral or scope information.

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 tool's behavior is well covered: what it reads, what it filters, and the safety cap. It does not describe return format or error handling, but for a read tool with a simple schema, this is reasonably complete.

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 references node_path and indicates it is the target node for reading settings, but does not explain the path format or expected structure. Since schema coverage is 0% and this is the only parameter, more detail would be helpful, but the reference provides some meaning.

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 tool reads whitelisted parm values for a given node_path, with a specific verb and resource. It distinguishes itself from siblings like set_render_settings (write operation) and get_parameter (generic) by narrowing to render settings and explicit renderer types.

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 implies usage for reading render settings but does not explicitly state when to use this over alternatives or when not to use it. It mentions filtering behavior but no direct comparison to sibling tools.

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