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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the ancient-order note, bitter-before-pungent reversal, and the fact the matrix appears both per-taste and per-dosha. These are genuine behavioral traits an agent can't infer from the name or schema alone.

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?

Three sentences: the first states the resource, the second explains the ordering nuance, the third explains the dual-index return structure. Both non-obvious behaviors earn their place. The language is dense but not bloated, and the most important information (the resource and the matrix) is front-loaded.

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 read-only list tool with fully documented parameters and safety annotations, the description covers the domain, the ordering surprise, and the return structure. No output schema exists, but the description compensates by explaining what the matrix contains and how it is indexed. It does not specify the exact JSON field names, but that level of detail is generally unnecessary for tool invocation.

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 100%, so all four parameters (lang, limit, offset, compact) are already documented with types, ranges, defaults, and even token-efficiency notes. The description adds no parameter information but does not need to; it focuses on the return data shape, which is the correct division of labor.

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 opens with a specific verb-resource pair: 'Return the six rasas, the tastes of Ayurveda...' and immediately specifies the distinctive eighteen-cell matrix behavior. It clearly distinguishes this from sibling tools like get_ayurveda_doshas or get_ayurveda_qualities by naming the rasa domain and the bidirectional dosha matrix. The title is also informative.

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 makes clear the tool returns the rasa-to-dosha matrix read in two directions, which is the core use case. It does not explicitly state when to prefer this over sibling tools, but it names the specific resource and its unique matrix layout. It could have mentioned 'for dosha-specific lists, use get_ayurveda_doshas' but the context signals and sibling names make the domain boundary reasonably clear.

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