get_node_schema

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'Get' implying a read operation, but offers no details on safety, side effects, authentication, or return format. Additional context (e.g., 'returns a JSON schema') would be beneficial.

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?

Exceptionally concise: a single sentence that front-loads the key requirement ('REQUIRED') and communicates purpose without extraneous 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 tool with 2 parameters and no output schema, the description is minimally adequate. It states the purpose and when to use, but omits the return value (schema) and assumes understanding of 'config schema'. Could be more complete about the output.

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 50% (only block_type documented). The description adds no parameter details beyond the schema, failing to explain app_id or provide format/restrictions. More parameter guidance is needed.

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?

Clearly states the action 'Get' and resource 'config schema for node type'. The prefix 'REQUIRED before configuring a node' adds strong context and distinguishes it from sibling tools like add_node and edit_node.

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?

Explicitly marks the tool as a prerequisite ('REQUIRED before configuring a node'), giving clear when-to-use guidance. Does not mention when not to use or alternatives, but the context is sufficient given no similar sibling for schema retrieval.

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