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

No annotations are provided, so the description carries full burden. It uses 'author' which implies a write operation, but does not disclose side effects, required permissions, or other behavioral traits. The lack of transparency is a significant 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 description is overly terse—a single sentence that barely explains the tool. While concise, it sacrifices clarity and structure. Every sentence should earn its place; this one does not provide enough value.

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 has 4 parameters, no output schema, and a large sibling context, the description is completely inadequate. It does not explain the purpose of the 'why' parameter, the effect of authoring it, or how to use the tool effectively.

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% (descriptions for 'why' and 'name' only). The tool description adds no additional parameter information. Parameters 'npub' and 'dpop_token' are undocumented beyond defaults. The description fails to compensate for the coverage 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?

Description states the tool authors the 'authoritative why' for a capability, but the phrasing is vague and does not differentiate from similar tools like cypher_suggest_capability_why or cypher_explain_capability. The verb 'author' implies writing, but the resource and action are unclear without context.

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 given on when to use this tool versus alternatives. The sibling list includes cypher_suggest_capability_why and cypher_explain_capability, which might be related, but the description offers no comparison or usage context.

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