qui_refresh_rss_item

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

With no annotations, the description bears full responsibility for disclosing behavior. It only states the HTTP method and endpoint, implying a mutation (POST) but not explaining what 'refresh' does, whether it is destructive, if it is asynchronous, or what side effects occur. No behavioral context beyond the endpoint is provided.

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, immediately front-loaded with the action and endpoint. It logically separates the argument passing conventions into a concise clause. Every word serves a purpose, with no 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?

Despite having an output schema, the description is insufficient for correct invocation. It does not explain what path variables are required (e.g., instanceID), whether query parameters are needed, what the request body should contain, or the expected response/behavior. The generic schema and one-sentence description leave significant gaps for an agent to fill.

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 input schema is a generic envelope with an 'arguments' object and no property details, so the description's instruction to pass path variables directly, query values in arguments.params, and body in arguments.body adds some structure. However, it does not list specific path variables, query parameters, or body fields, leaving the agent to infer from the endpoint placeholder. It offers moderate semantic value but incomplete guidance.

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 identifies the exact HTTP method and endpoint (POST /instances/{instanceID}/rss/items/refresh), which is a specific action on a specific resource. The verb 'refresh' and resource 'RSS items' clearly distinguish this from all sibling tools, including other RSS-related tools like qui_get_rss_items or qui_remove_rss_item.

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 provides no guidance on when to use this tool versus alternatives. It only gives technical call instructions, with no mention of use cases, prerequisites, or situations where another tool would be more appropriate. The agent is left to infer the purpose from the name alone.

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