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

The verb 'Read' implies a safe, idempotent operation with no destructive side effects. However, without annotations and given the minimal description, the agent gets no explicit confirmation of safety, permissions, or return format. The implied behavior is clear but not detailed.

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, front-loaded with the verb, and contains no superfluous words. It is highly efficient and directly conveys the tool's purpose.

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 parameterless read tool with a clear file path, the description is sufficient. However, it does not explain the relationship to rubrkit_read_api_doc or why 'canonical' matters, leaving minor ambiguity in a rich sibling context.

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 has no parameters (100% coverage by absence), so the description adds nothing beyond the schema. Baseline 3 is appropriate per rules.

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?

Description clearly states the action (Read) and the specific resource (the canonical docs/api/openapi.yaml contract). The term 'canonical' helps distinguish from sibling tools like rubrkit_read_api_doc, which likely reads a different API document.

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 its siblings. It does not explain what makes this the 'canonical' contract or contrast with other read tools such as rubrkit_read_api_doc or rubrkit_search_api_docs.

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