plugins.get_all_plugins

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

Beyond the readOnly and destructive annotations, the description reveals meaningful behavior: paginated requests to GET /api/v1/plugins, collection of all pages, and return as a single flat list. It also documents minimum fields in the return objects, though it stops short of describing error or empty-list behavior.

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 front-loaded with the purpose, followed by pagination behavior and a concise bulleted return contract. Every sentence carries useful information and the bullet list makes the return fields easy to scan.

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 parameterless, read-only list operation, the description sufficiently covers purpose, pagination, aggregation behavior, and return shape. The explicit Returns section compensates for the absence of an output schema, and the annotations already cover the safety profile.

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 has zero parameters and the schema confirms an empty properties object, so the 0-parameter baseline of 4 applies. The description appropriately focuses on behavior and return shape rather than inventing parameter details.

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 specific operation: 'Retrieve all plugins installed on the Sisense instance.' It reinforces scope with 'complete plugin list' and the exact API endpoint, making it easy to distinguish from sibling tools focused on dashboards, datamodels, folders, and reports.

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 clear context by explicitly saying it retrieves all plugins and that all pages are collected, so an agent knows to call this when the full plugin list is needed. It does not name alternatives, but no plugin-specific sibling appears in the provided tool list, so explicit exclusions are less necessary.

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