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 meaningful behavioral context beyond that: the response deliberately reports a recorded commentary disagreement rather than resolving it silently, and explains why that choice matters for dosha linkage. This is exactly the kind of non-obvious behavior that helps an agent trust and interpret the result.

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 dense but efficient, front-loading the core purpose and then adding only consequential detail about the commentary disagreement. Every clause contributes useful information. It is slightly longer than the minimal ideal, but not padded, and the structure is logical.

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 that there is no output schema, the description adequately explains what the response contains: the ten opposed pairs, each member's action word, the half-verse rule, and the dosha associations. It also flags the one ambiguous pair. The remaining invocation details like pagination and response language are fully covered by the parameter schema, so nothing critical is missing.

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?

Parameter schema description coverage is 100%, so the baseline is 3 even though the tool description adds no parameter-specific guidance. The description does not discuss lang, limit, offset, or compact, but the schema already documents each with defaults, ranges, and meanings. No additional parameter insight is needed.

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 and resource: 'Return the twenty gunas, the qualities of Ayurveda, as the ten opposed pairs...' This is far more specific than the title and clearly identifies the unique deliverable among the sibling tools, especially by noting the link to doshas. No agent could mistake this for get_ayurveda_tastes or get_ayurveda_doshas.

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 it implicitly clear this tool is for retrieving the guna pairs, but it never explicitly states when to use it versus alternatives such as get_ayurveda_tastes or get_ayurveda_doshas. There is no when-not-to-use guidance or named sibling alternative, so usage is implied rather than directed.

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