hs4.plugins.function.call

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

No annotations are provided, so the description must carry the full burden. It only says 'call pluginfunction endpoint', which implies an action but does not disclose whether it is destructive, what side effects occur, or any authorization requirements. The schema hints at mutability via 'confirm' and 'dryRun', but the description is silent.

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 short sentence, which is concise but lacks structure. It would benefit from a brief explanation of the tool's purpose in one or two sentences without being verbose.

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?

Given 8 parameters, no output schema, and no annotations, the description is inadequate. It does not explain the domain (plugin functions), how to use the parameters, or the return value. The tool is complex and the description underdelivers.

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 description only mentions 'positional P1..Pn parameters' which loosely references the 'params' array but does not clarify any other parameters. With 50% schema coverage, the description should add meaning, but it adds nothing beyond the schema.

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 it calls a plugin function endpoint with positional parameters, which is specific enough to convey the core action. However, it does not explain what a 'plugin function' is, leaving some ambiguity about the domain.

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?

No guidance on when to use this tool versus other plugin-related tools in the sibling list (e.g., hs4.plugins.list, hs4.admin.plugins.*). The description does not specify context or alternatives.

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