users_get_user_accessible_nodes

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the HTTP verb — no return shape, no pagination, no auth/permission requirements, no note on whether access is scoped by squad or by node status. For a completely bare definition this is a real 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?

It is short and the operation is stated first, but it carries raw OpenAPI boilerplate (the path line and 'Tags: Users Controller') that adds no value to an agent. Efficient in size but not fully earned.

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 no annotations, the description must explain what 'accessible nodes' means and what the response contains; it does neither. For a simple one-parameter read this is the minimum raw payload rather than a complete definition.

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%, and the single required parameter (userId, number > 0) is undocumented. The description only embeds it in the raw path template, leaving ambiguous whether it expects an internal numeric ID or a UUID/short-UUID — an important distinction given sibling tools that key on short_uuid and username.

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 does convey a specific verb+resource ('Get user accessible nodes'), so an agent can tell it retrieves nodes reachable by a user. However it is essentially a restatement of the endpoint path and gives no differentiation from neighbors like internal_squad_get_internal_squad_accessible_nodes or nodes_get_nodes.

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, no prerequisites, and no mention of the sibling tools that also return node sets (nodes_get_nodes, internal_squad_get_internal_squad_accessible_nodes). Only the implied read semantics of a GET hint at context.

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