get_node_integration

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 adds the '[READ]' marker and the underlying endpoint (GET /api/node-integrations/:uuid), which is mildly useful context but not behavior beyond the annotations. It does not describe what a 'node integration' contains or how errors (missing uuid) surface.

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 terse lines with the resource and key front-loaded and no filler. The endpoint line is arguably redundant with the name, but it costs little and is not padding.

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-record fetch with one well-constrained uuid and no output schema, the definition is minimally sufficient. It never says what a node integration is or what the response contains, which matters for an agent deciding between this and the plural list tool.

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 parameter is self-documenting: 'uuid' with format=uuid and a strict regex pattern. The description's 'by uuid' phrasing confirms the lookup key but adds no format, scope, or example detail beyond the 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?

States a specific verb and resource ('Get Node Integration by uuid'), so an agent knows it fetches a single integration record. However, it does not distinguish itself from the sibling 'get_node_integrations' (plural/list) beyond the singular resource name, leaving the singular-vs-collection distinction to inference.

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?

There is no guidance on when to use this tool versus 'get_node_integrations', 'get_node', or the other node-related getters in the sibling list. The HTTP route is included but no context, prerequisites, or alternative selection criteria are given.

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