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

No annotations are provided, so the description carries the full behavioral burden. It notes the score can be null when unscored, which is useful, but it says nothing about read-only safety, permissions, error behavior for missing nid/eid, or any other trait beyond the return value already covered by the output schema.

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?

A single short sentence that front-loads the endpoint and follows with the return nuance. Efficient, though the 'one result of query' clause is more confusing than informative.

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?

The output schema exists, so return values needn't be re-explained, and the core fetch purpose is conveyed. However, with 0% parameter documentation and no annotations, the definition leaves the agent guessing about parameter meaning and behavioral traits.

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 neither parameter has a description, so the description must compensate. It only echoes the {nid} and {eid} path placeholders without explaining what a node id or edge id is, their format, or whether eid is scoped to nid.

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 names a concrete verb (GET) and a specific resource path (/nodes/{nid}/edges/{eid}), so the agent can tell it fetches a single edge. The phrase 'one result of query `nid`' is vague and it never distinguishes itself from siblings like list_edges or get_node, but the endpoint makes the purpose clear.

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 statement of when to use this tool versus list_edges, get_node, or the other edge tools. The single-edge fetch is only inferable from the URL template, not from any explicit guidance or exclusion.

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