get_node_plugin

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description's only additional content is the '[READ] GET /api/node-plugins/:uuid' line, which merely restates the annotation and HTTP route rather than disclosing return shape, error behavior, or access requirements.

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?

Two short lines with the essential resource and identifier front-loaded and no wasted prose. The endpoint/verb line is somewhat redundant with the annotations but does not bloat the definition.

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 single-parameter read tool with a fully constrained schema and safety annotations already present, the definition is adequate to invoke correctly. It omits any indication of what the plugin object contains, which is a minor gap given no output schema exists.

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%, but the single uuid parameter is heavily constrained by the schema's format=uuid and regex pattern. The description adds only 'by uuid', which is minimal; it neither expands on the identifier's origin nor compensates meaningfully for the absent prose description.

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 (Get) and resource (Node Plugin) with a scope qualifier (by uuid), which implicitly separates it from the sibling list tool get_node_plugins. However, it does not explicitly name the sibling, so the agent must infer the singular/plural 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?

Usage is only implied: retrieve a single node plugin keyed by uuid. There is no explicit when-to-use statement, no exclusion ('use get_node_plugins to list all'), and no prerequisites, but the singular resource plus required uuid makes the intent reasonably clear.

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