get_node_metadata

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

With no annotations, the description must convey all behavioral traits. It only states 'Get metadata' without specifying the nature of the metadata (e.g., fields, format) or any side effects. Since it is a read operation with no parameters, more detail on the output structure would improve transparency.

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, front-loaded sentence that efficiently conveys the tool's purpose. However, it could be slightly expanded with minimal detail about the output without losing 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 and the presence of an output schema, the description is adequate. However, it does not explain what 'MetaNode nodes' are, which may be unclear without domain knowledge. The tool is complete for its narrow scope but could benefit from clarifying the term 'MetaNode'.

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 input schema has zero parameters, so there is no need for parameter descriptions. Schema description coverage is 100% because there are no parameters to document.

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 the tool retrieves metadata for all nodes from MetaNode nodes in the knowledge graph. It distinguishes itself from sibling tools like get_neo4j_schema (broader schema) and get_relationship_metadata (focused on relationships) by specifying the exact scope (MetaNode nodes).

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 such as query or get_neo4j_schema. The description does not mention any prerequisites, context, or exclusion criteria, leaving the agent to infer usage from the tool's name and sibling list.

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