divine_get_matching_manglik

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description does not contradict them. It adds context about comparison behavior, but does not disclose additional details such as output structure or edge-case behavior.

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 short, front-loaded with the main purpose, and has no filler beyond a slight redundancy between 'both people' and 'both individuals.' It is easy to scan.

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?

The presence of an output schema and read-only annotations reduces the need for the description to explain return values and safety. Still, the minimal description leaves gaps around parameter requirements and when to choose this tool over the single-person divine_get_manglik_dosha.

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 0%, and the description does not compensate by explaining that full birth details for both persons are required or how the p1_* and p2_* fields are organized. It only implies that two people are involved.

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 action: checking Manglik Dosha for both people in a matchmaking context and comparing their statuses for marriage compatibility. It is specific and helps distinguish this from non-matching tools, though it does not explicitly contrast it with the sibling tool divine_get_manglik_dosha.

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 phrase 'in a matchmaking context' and 'when either person is Manglik' imply when the tool should be used. However, it does not explicitly state when not to use it or point to the single-person Manglik alternative.

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