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

With no annotations, the description carries the full burden of behavioral disclosure. 'Browse' hints at a read-only operation, but the description does not mention authentication requirements, response shape, pagination behavior, or whether it returns full tool metadata.

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 short and front-loaded with no wasted words, but it is under-specified for a tool with four parameters and no annotations. Its brevity reads more like a stub than a complete, useful definition.

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 four-parameter tool with no output schema and no annotations, this definition is too thin to invoke reliably. It lacks parameter semantics, category constraints, and any sense of what the returned catalog data looks like.

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?

Schema description coverage is 0%, yet the description adds nothing about q, limit, offset, or category. 'q' is especially ambiguous, and no acceptable category values are provided even though the schema has no enums.

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 uses 'Browse' as a specific verb and identifies the resource as 'Qorevia live paid tools,' so an agent can infer this is a listing/catalog tool. It does not explicitly distinguish it from siblings like qorevia_find or qorevia_tool_info, but the catalog/browse framing provides reasonable separation.

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 is given on when to use this tool versus alternatives such as qorevia_find for searching or qorevia_tool_info for inspecting a single tool. The appropriate context must be guessed from the tool name and sibling list.

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