get_internal_squad_accessible_nodes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's '[READ]' tag merely duplicates that. It adds no behavioral context beyond the annotations: no note on what 'accessible nodes' means, whether results are paginated, or what permissions are required to read another squad's node set.

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?

Two short lines with zero preamble, so it is front-loaded and compact. The '[READ]' tag is redundant with the annotations, and the brevity reflects under-specification rather than disciplined concision.

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?

For a single-parameter read with no output schema and annotations covering the safety profile, this is minimally adequate. It still omits any indication of what the returned node list contains or how 'accessible' is determined, which is exactly the gap an agent would need filled.

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 there is one required 'uuid' parameter. The embedded path '/api/internal-squads/:uuid/accessible-nodes' does implicitly identify the uuid as an internal squad UUID, adding a small amount of meaning over the bare schema. That is better than nothing but far short of documenting the identifier's source or format.

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 gives a specific verb+resource ('Get internal squad accessible nodes') plus the HTTP route, so the agent knows this returns the node set reachable by an internal squad. However, it adds little beyond restating the tool name and does not distinguish it from siblings like get_internal_squad, get_internal_squad_usage, or get_user_accessible_nodes. Purpose is identifiable but not sharpened.

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 conditions, and no pointer to alternatives such as get_user_accessible_nodes or get_internal_squad. The agent must infer the scenario entirely from the name.

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