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

No annotations are provided, so the description carries the full burden. It states 'Ground' which implies a state change or association, but offers no details on side effects, permissions, reversibility, or impact on existing links. This is insufficient for a likely mutation tool.

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 with no wasted words. However, given the tool's role and sibling context, it could benefit from slightly more detail without losing conciseness, but it's still efficient.

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?

No output schema exists, and 50% of parameters lack schema descriptions. The description should compensate by explaining return values, side effects, or parameter usage. It does not, leaving the agent underinformed about the tool's behavior and output.

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 50% (name and patent_ref have descriptions; npub and dpop_token lack descriptions). The description adds no extra meaning beyond the schema, merely echoing 'invariant' and 'patent reference numeral'. It does not help with the undocumented parameters, which have defaults but no semantic guidance.

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 'Ground an invariant in a patent reference numeral' clearly states the action (ground) and resources (invariant, patent reference numeral). It distinguishes from sibling tools like 'cypher_assert_invariant' and 'cypher_link_capability_to_patent' by focusing on linking an invariant to a patent reference.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools include many linking operations (e.g., 'cypher_link_capability_to_patent', 'cypher_link_issue_to_capability'), but the description fails to specify conditions or prerequisites for using this specific tool.

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