risha_get_operation

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

No annotations provided; description mentions included details but does not disclose idempotency, authorization needs, or rate limits. Adequate but lacks depth for a non-annotation context.

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?

Single sentence that efficiently conveys purpose. Could be slightly more structured but is not wasteful.

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?

Adequate for a simple tool with one parameter and no output schema, but lacks guidance on obtaining the operationId (e.g., via sibling 'risha_list_operations') and expected return format.

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 coverage is 0%; description only mentions 'including required path/query parameters' without explaining what 'operationId' is or how to obtain it. Does not add meaning beyond 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?

Clearly states the verb 'Get details', resource 'one Risha API operation', and includes scope 'required path/query parameters and request body schema'. Distinct from sibling like 'risha_list_operations'.

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?

Implies usage for retrieving details of a specific operation, but does not explicitly contrast with siblings like 'risha_list_operations' or mention when not to use.

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