squads_accessible_nodes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing: no indication of return shape, whether results are paginated, or whether 'accessible nodes' is computed per-user or per-squad. With annotations doing the safety work, the remaining behavioral burden is unmet.

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?

One short, front-loaded sentence with zero padding, so it is structurally clean. However, the brevity comes at the cost of under-specification rather than genuine economy.

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?

A read-only lookup with no output schema and an undocumented required identifier leaves the agent unable to predict either input meaning or result content. For a one-parameter query tool the description should at minimum name the entity the UUID refers to.

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 0%, so the description must explain the single required 'uuid' parameter. It does not: an agent cannot tell whether this is a squad UUID, a user UUID, or a node UUID, which is the single most consequential ambiguity for calling this tool correctly.

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 restates the tool name almost verbatim: 'Get internal squad accessible nodes' for squads_accessible_nodes. It does not clarify what an 'accessible node' is in this domain (nodes a squad's users can reach? nodes bound to a squad?) nor how this differs from squads_get or users_accessible_nodes. The verb+resource pattern is present but the semantics are opaque.

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 guidance on when to call this versus siblings such as squads_get, nodes_get, or users_accessible_nodes, which all plausibly return overlapping node information. No prerequisites, no conditions, no exclusions are stated.

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