get_adapters

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Get all adapters', which implies a read operation, but it does not explicitly state that it is safe/read-only, mention potential large response sizes, pagination, or any side effects. The description is too terse to shoulder the disclosure burden.

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 description is a single, front-loaded sentence with no filler. Every word contributes to specifying the tool's purpose, making it highly concise and well-structured.

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 simple list-all tool with an output schema present, the description is nearly complete. It states what is returned (adapters) and the scope (configured on the platform instance). It does not mention edge cases like error behavior or authentication, but these are less critical given the simplicity and presence of that output schema.

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?

There are zero parameters, so the schema already exhaustively documents inputs. With no params, the baseline is 4, and the description's phrase 'all adapters' reinforces that no filtering is needed. No additional parameter meaning is required.

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 clearly states the verb 'Get' and the resource 'all adapters', with scope 'configured on the Itential Platform instance'. This distinguishes it from sibling tools like get_applications or start_adapter by explicitly naming the adapter resource.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor any exclusions. Usage is only implied by the name 'get_adapters', which is straightforward but lacks explicit context for choosing it over other list/get tools.

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