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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Upsert' (implying insert-or-update) but fails to explain idempotency, whether partial updates are allowed, what 'the graph' refers to, authentication requirements, or side effects on existing data. This is insufficient for a tool with 14 parameters.

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 extremely concise (one sentence, 8 words), but at the expense of necessary detail. It earns its place by stating the core purpose, yet for a 14-parameter tool with no annotations or output schema, it is under-specified – sacrificing completeness for brevity.

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 complexity (14 parameters, no output schema, no annotations), the description is too sparse to enable correct invocation. It omits critical context such as identity semantics (e.g., `number`+`repo_name` as composite key), scope of 'live state', and expected return behavior, making it incomplete for reliable use.

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 86%, so the input schema already documents most parameters well. The description adds no parameter-level or usage context beyond what the schema provides, but given high coverage, baseline score 3 is appropriate.

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 action ('Upsert') and the resource ('live state of a GitHub PR into the graph'), making the tool's primary function unmistakable. It distinguishes from sibling tools like `cypher_list_pull_requests` (read-only list) or `cypher_pr_provenance` (provenance query), though it does not explicitly name alternatives.

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?

The description offers no guidance on when to use this tool versus other PR-related siblings (e.g., `cypher_link_pr`, `cypher_list_pull_requests`). There is no mention of prerequisites, exclusions, or typical use cases, leaving the agent to infer appropriateness solely from the name.

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