get_parameter_schema

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

No annotations are provided, so the description carries full disclosure burden. It usefully warns that nodes commonly have dozens to 100+ parameters, implying large payloads and motivating the filters. Beyond that output-size caution, it says nothing about permissions, read-only nature, or return shape.

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?

Front-loaded purpose, then a high-value warning/usage rule, then the Args block. Sized well for a 3-param tool. Uses some vertical space but each line adds 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?

For a 3-param introspection tool with no annotations and no output schema, the description covers purpose, filtering strategy, and parameter meaning. The one omission is what the returned 'schema' actually contains (types, defaults, ranges), which an agent might want to know.

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 coverage is 0%, so the description must compensate, and it largely does via the Args block: parm_name is 'exact parameter name for a single-parameter lookup' and filter is a 'case-insensitive substring match against name or label.' Only node_path ('Node path') is thin.

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?

States a specific verb and resource: 'Get the template schema for parameter(s) on a node.' This clearly separates it from value-oriented siblings like get_parameter/get_parameters, though it never names those siblings explicitly to reinforce the distinction.

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?

Gives concrete operational guidance ('Always use parm_name or filter unless you genuinely need the full list'), which is a strong usage steer. However it doesn't state when to prefer this tool over sibling lookups like get_parameter or get_parm_template_tree.

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