ruyi_list_preload_scripts

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only mentions the output (scriptId and content summary) and does not state whether the operation is read-only, requires an active browser, or has any side effects. The verb 'list' implies read-only, but this is not explicitly disclosed.

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 sentence that is concise and front-loaded with the primary action and result. Every word adds value, and there is no unnecessary filler or redundancy.

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 tool has a simple purpose but includes an undocumented parameter that suggests paging or filtering. The description lacks explanation of this parameter and does not provide enough contextual detail (e.g., whether it operates on the current page or across the session). The absence of an output schema is partially mitigated by the mention of scriptId and summary, but overall completeness is lacking.

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 schema has one parameter 'pageIdx' with a default of 0 and no description in the schema. The description does not mention this parameter at all, leaving its meaning and purpose completely unexplained. With 0% schema description coverage, the description fails to compensate, providing no added value.

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 all injected preload scripts with scriptId and content summary, which is a specific verb+resource scope. It differentiates from siblings like 'ruyi_list_scripts' by specifying 'preload' scripts, making the purpose unambiguous.

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 guidance on when to use this tool versus alternatives (e.g., 'ruyi_list_scripts') and does not mention any exclusions or prerequisites. Usage is only implied from the purpose, but there is no explicit context or comparison.

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