formalize_tex

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions writing to sibling directories, implying a write operation, but doesn't cover critical aspects like permissions needed, error handling, whether it overwrites existing files, or performance characteristics. This leaves the agent with insufficient information about the tool's 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 extremely concise and front-loaded, with every sentence earning its place. The first sentence defines the pipeline, and the second specifies output locations. There's no wasted verbiage, making it efficient for an agent to parse.

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 the tool's complexity (processing pipeline with file outputs) and no annotations, the description is incomplete. It covers the high-level flow and output destinations but lacks details on error cases, side effects, or dependencies. The presence of an output schema helps, but more behavioral context is needed for a higher score.

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%, so the schema provides no parameter details. The description adds some value by implying 'tex_path' is the input TeX file and 'module_name' influences the output Lean module, but it doesn't explain parameter formats, constraints, or defaults. This partial compensation meets the baseline for low 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?

The description clearly states the tool's purpose: it's an end-to-end pipeline that processes TeX files to generate Formath JSONL and Lean stub modules. It specifies the verb ('formalize') and resources (TeX files), though it doesn't explicitly differentiate from sibling tools like 'tex_extract' or 'workflow_formalize_all', which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It mentions output directories but doesn't explain prerequisites, when to choose this over 'tex_extract' or 'workflow_formalize_all', or any constraints. This lack of contextual usage information is a significant gap.

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