get_node

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

Annotations declare readOnlyHint=true, so the agent already knows this is a safe read operation. The description adds no extra behavioral context beyond what annotations provide (e.g., no mention of error handling or response format). Since the annotation covers the key behavioral trait, the description is adequate but does not add value.

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 concise sentence with no wasted words. It is front-loaded with the core action. However, it could be slightly expanded to include parameter context without sacrificing conciseness.

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 the tool's simplicity (one parameter, no output schema), the description is very minimal. It does not explain the return value, possible errors (e.g., node not found), or any prerequisites. The agent is left guessing about the output, which is incomplete for a tool with no output schema.

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%, and the description fails to explain the 'name' parameter. The description says 'Get a specific node from Jenkins' but does not clarify that the parameter is the node name or identifier. The agent gets no added meaning from the description beyond the bare 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 'Get a specific node from Jenkins' clearly states the action (Get) and resource (a specific node from Jenkins). It distinguishes from siblings like get_all_nodes (which retrieves all nodes) and get_node_config (which gets configuration). The parameter 'name' implies retrieval by identifier, making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives like get_all_nodes or get_node_config. With many sibling tools, the agent receives no direction on choosing this tool over others, such as when a single node is needed by name versus listing all nodes or retrieving configuration.

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