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

No annotations exist, so the description must disclose behavior. It does not mention safety (read-only vs destructive), authentication needs, rate limits, or side effects. The description only states what the tool does, not its behavioral traits.

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 very short (one sentence) and front-loaded, but it sacrifices necessary detail. It is concise but lacks structure; there is no explanation of return value or how to interpret the output. It saves words but at the cost of completeness.

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?

With no output schema and 3 parameters (one undocumented), the tool description is insufficient for correct invocation. It does not explain what the tool returns, how to use the optional parameters, or any prerequisites. For a tool in a large sibling family, this is a major gap.

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?

Only 33% of parameters have schema descriptions (fqn has a minimal description). The tool description adds no additional parameter semantics for npub or dpop_token, failing to compensate for the low coverage. It does not explain the role of optional parameters.

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 states the tool pivots to a code symbol and lists several aspects it covers (service, capabilities, etc.), but the verb "pivot" is ambiguous and not immediately clear whether it means retrieve, navigate, or something else. It does distinguish from siblings which focus on single aspects, but could be more precise.

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. Given the large number of sibling tools, explicit usage context or exclusion criteria would help the agent decide correctly.

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