get_node

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

With no annotations, the description partially indicates that the response includes executor info, but lacks details on permissions, error handling, or read-only nature. The output schema likely covers return structure, but behavioral traits are minimal.

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 concise and front-loaded with the core purpose. However, the 'Args' section is redundant as it simply restates the parameter name without new info.

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?

Given a simple tool with one parameter and an output schema, the description covers the basic purpose. It lacks usage guidance and does not clarify when to use this versus get_all_nodes or get_node_config, leaving gaps for an agent.

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 only parameter 'name' has 0% schema description coverage. The description merely repeats 'The name of the node', adding no additional context like format, constraints, or examples.

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 'Get a specific node from Jenkins' and notes that it contains executor info about the node, distinguishing it from sibling tools like get_all_nodes and get_node_config.

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 on when to use this tool versus alternatives like get_all_nodes or get_node_config, nor any conditions or prerequisites.

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