metadata_get_node_metadata

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

No annotations are provided, so the description carries the full burden, and it discloses essentially nothing beyond the HTTP route: it does not say what metadata fields are returned, what happens when a node has no metadata (empty object vs 404), or whether any permission is required. For a metadata read with zero structured hints, this is a real gap.

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 purpose is front-loaded in an extremely short block, but the OpenAPI artifacts ('GET /api/metadata/node/{uuid}' and 'Tags: Metadata Controller') consume the majority of the text without adding information an agent can act on.

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?

With no output schema, no annotations, and an undocumented parameter, the description is too thin for an agent to call this confidently or interpret the result; it should at minimum describe the returned metadata shape and the not-found behavior.

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% for the single required uuid parameter, and the description only echoes it as {uuid} in the path template. It does not clarify that this is the node's UUID or how to obtain it, so it barely compensates for the schema gap.

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 clear verb+resource ('Get node metadata') and implies scoping by the {uuid} path parameter, which distinguishes it from metadata_get_user_metadata and metadata_upsert_node_metadata in the sibling list. The core purpose is legible even though the raw HTTP route and 'Tags: Metadata Controller' line add no meaning.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as metadata_upsert_node_metadata (write) or metadata_get_user_metadata (user-scoped variant). The agent must infer everything from the tool name.

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