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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The phrase 'most-connected' adds a useful ordering hint that the annotations cannot convey, but the description says nothing about what 'hub' means, how connections are counted, or how ties are broken.

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 front-loaded sentence with zero filler, and the key concept (most-connected hubs) comes first. It is appropriately sized for the tool, though it could have spent one clause on ordering or limit behavior without becoming bloated.

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, the description must carry the return-value burden, and it only indicates that results are notes ordered by connectivity. It omits what fields come back, what counts as a 'hub', and pagination behavior, leaving real gaps for a discovery tool.

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 100% for the single 'limit' parameter (type, default 20, min 1, max 100), so the schema fully documents it. The description adds no extra parameter meaning such as ordering interaction with the limit, so the baseline of 3 applies.

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 pairs a specific verb (list) with a specific resource (hub notes) and a scope qualifier (most-connected, in the vault). It is distinguishable from generic siblings like list_notes or search_notes, though it never explicitly contrasts itself with them.

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 when-to-use guidance and no mention of alternatives such as list_notes, search_notes, or get_backlinks, which all surface note-related results. An agent must infer that this tool is for discovering highly-linked notes rather than querying them.

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