risha_list_operations

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

No annotations are provided, so the description carries full burden. It only states it lists operations and supports filtering, but does not disclose data freshness, pagination behavior, rate limits, or the read-only nature. Key behavioral details are missing.

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 extremely concise with two sentences, front-loading the purpose and then providing immediate usage guidance. Every word carries weight with no 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?

Given the tool has four parameters, no output schema, and no annotations, the description is incomplete. It does not explain the limit parameter's role in pagination, the meaning of tag and method filters, nor the structure of the returned operation list.

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 only 25% (filter has a description). The tool description adds value by explaining filter searches operationId, path, tag, or summary, but other parameters (tag, limit, method) are left without explanation beyond the schema types.

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 Risha API operations from a Swagger document, with a specific verb (list) and resource (operations). It distinguishes from siblings like risha_get_operation by implying a broad listing, and mentions filtering for search.

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 clear context for using the tool (listing operations, filtering), but does not explicitly state when not to use it or name alternative tools like risha_get_operation for specific operations. No exclusions are given.

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