node_plugin_get_all_shared_lists

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the exact return shape (name, type, item count only) and that the endpoint is a Preview surface, but says nothing about authentication/permissions, pagination, or whether the list can be large. Partial disclosure for a no-annotation 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 functional sentences are front-loaded and waste-free: what it returns, then the alternative for getting items. The raw "GET /api/..." line and the trailing "Tags: Node Plugins Controller" are metadata noise that adds nothing for an agent, keeping it out of 5.

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 convey returns, and it does so precisely (name, type, item count) plus a pointer to the detail tool. Only the auth/pagination/scale context is absent, which is minor for a zero-parameter read listing.

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?

The tool takes zero parameters and the schema is trivially complete, so the baseline is 4. There is no parameter behavior left for the description to compensate for; the mention of "every shared list" merely confirms the unfiltered, no-argument scope.

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?

States a specific verb and resource (Get Shared Lists) and precisely scopes the payload: only name, type and item count of every shared list. It also distinguishes itself from the sibling node_plugin_get_shared_list_by_name by name, so an agent can route without opening either schema.

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?

Explicitly routes the agent: use "Get Shared List by name" to fetch the items themselves, which tells the caller this tool is the summary/listing step. No explicit when-not conditions or prerequisites (e.g. auth) are given, so it falls short of a full 5.

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