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

With no annotations, the description carries the full behavioral burden. It does add real context not in the schema: the operation POSTs to a remote endpoint (cuni-studio /api/bank) and may 'refuse', implying validation. However, it omits auth requirements, side effects, and reversibility.

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 text is short but the front-loaded metaphor ('paste N, get X', 'Ingest → emit → prove, or refuse') consumes space without conveying usable meaning, so it is not well-structured or front-loaded with the actual purpose.

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?

There is no output schema and no annotations, so the description must explain inputs and outputs. It never describes the result of the transform, what 'prove' returns, or failure modes, leaving the agent without enough to call it confidently.

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 the baseline is 3. The description repeats the arg names with brief glosses (py|cuni, catalog id e.g. js) that roughly match the schema, adding no syntax or format detail beyond it.

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 tagline 'paste N, get X' and 'Ingest → emit → prove, or refuse' are cryptic metaphors that never state plainly what the tool converts or produces. The args hint at a Python-to-catalog-language transform, but the agent must infer that, and the tool is not distinguished from siblings like cuni_get/cuni_search.

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?

There is no statement of when to use this tool versus cuni_get, cuni_search, or any other sibling. 'v1 from Python' implies a version/scope but no explicit conditions or exclusions are given.

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