Composition Validator

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

Description mentions method (equation and timeline checks) but lacks details on side effects, permissions, return format, or handling of invalid input. With no annotations, it provides moderate but incomplete behavioral 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 concise sentence with no waste, but could be better structured with separate purpose and parameter details.

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 high complexity (5 parameters, nested object, no output schema, no annotations), the description is severely incomplete, missing explanations of input structure and validation output.

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?

Description does not explain any of the five parameters (taal, form, jati, cycles, composition_input) beyond the schema, which has 0% description coverage.

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 tool validates user-entered tihai, tukra, or chakradhar structures using equation and timeline checks, distinguishing it from siblings like compose_builder or composition_transposer.

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 alternatives (e.g., practice_coach) or what prerequisites are needed.

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