Fl Plugin Params

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

No annotations are provided, and the description does not mention side effects, permissions, or error behavior. It is reasonable to infer a read-only operation, but this is not explicitly stated, so transparency is incomplete.

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 concise sentence that conveys the action, result fields, and key features without unnecessary detail.

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?

The description lacks essential context for proper usage, particularly the meaning of the required 'index' parameter and the role of 'slot'. Since no output schema is provided, the agent cannot fully understand the expected result shape, making it incomplete for reliable invocation.

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?

Only 'filter' and 'offset' are explained in the description. The required 'index' parameter and 'slot' and 'max_params' are not described, leaving their meaning and usage ambiguous. Schema coverage is less than 50%, and the description does not compensate.

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 tool lists plugin parameters and specifies the fields returned (index, name, normalised value, display string) along with filtering and pagination options. This distinguishes it from sibling tools like fl_plugin_set_params or fl_plugin_info.

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 implies usage for reading plugin parameters without modifying them, and mentions filtering by substring and paging with offset. However, it does not explicitly state when to use this over other parameter-related tools (e.g., fl_plugin_set_params).

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