get_parameter_schema

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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only operation via 'Get' and describes the output as the full parameter schema, but it does not specify behavior for invalid node paths, return structure, or potential side effects. This is adequate for a simple getter but not rich.

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, front-loaded sentence with no filler. The parenthetical '(all parm templates)' clarifies the term 'parameter schema' without unnecessary verbosity.

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 one-parameter, read-only tool, the description covers the essential purpose and input. However, the absence of an output schema and annotations means the description could usefully mention path format or return structure. It is minimally viable but leaves some gaps for a smooth agent interaction.

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?

Schema description coverage is 0%, so the description must compensate. It only says 'for a node,' which largely restates the node_path parameter name without adding format details, examples, or constraints. The parameter is self-explanatory in isolation, but the description adds little beyond the schema.

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 action ('Get') and the specific resource ('full parameter schema (all parm templates) for a node'). This directly distinguishes it from sibling tools like get_parameter (which fetches parameter values) and get_node_doc (which retrieves documentation).

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 usage context is implied: use this tool when you need the complete parameter template list for a node. However, there is no explicit guidance on when not to use it or mention of alternatives such as get_parameter for parameter values.

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