to_citable_mql

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

No annotations provided, so description carries full burden. It discloses deterministic behavior: 'indentation becomes brackets, spaces become AND, string features get quoted from the catalogue.' Also explains refusal of complex templates with explanation.

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?

Two paragraphs, clear and front-loaded. First sentence defines purpose, second adds details. No wasted words, though 'Deterministic, no model involved' is somewhat unnecessary. Efficient overall.

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 one parameter, no output schema, and moderate complexity (language conversion), the description covers behavior, limitations, alternatives, and transformation rules. Complete for agent usage.

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 only parameter 'template' has no schema description (0% coverage). The description explains it is a Text-Fabric search template and gives transformation rules, adding meaning beyond the schema. Lacks explicit syntax examples but sufficient for use.

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 tool converts a Text-Fabric search template to MQL for SHEBANQ, with a specific verb 'Convert' and resource. It explicitly distinguishes itself as the mirror of 'to_tf_template', differentiating from siblings.

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?

Provides explicit use case: 'Use this to turn a notebook query into a citable SHEBANQ saved query.' Also states when not to use: 'Templates using TF constructs beyond ... are refused with an explanation.' Mentions the alternative tool 'to_tf_template' as the mirror.

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