Formath MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return format ('JSON array of results per file') and naming behavior, which adds some context. However, it doesn't describe what 'formalize' entails operationally (e.g., what transformations occur), potential side effects, error handling, or performance characteristics. For a batch processing tool with zero annotation coverage, this leaves significant behavioral gaps.

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 with only three sentences, each delivering essential information: scope, parameter behavior, and return format. It's front-loaded with the core action and wastes no words. The structure efficiently communicates key details without redundancy.

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 2 parameters, 0% schema coverage, no annotations, but with an output schema (which handles return values), the description provides adequate context. It covers the tool's scope, parameter semantics for naming, and output structure. However, it lacks details on what 'formalize' means operationally and any prerequisites, which would be helpful given the complexity of batch file processing.

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 description must compensate. It explains the 'naming' parameter's behavior ('by_file' → module name from file stem, otherwise use "Main") and implies 'project_root' specifies the directory path. This adds meaningful semantics beyond the bare schema, though it doesn't detail parameter constraints or formats. With 2 parameters and good clarification of the optional one, it earns above baseline.

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 ('Formalize all *.tex') and target resource ('under <project_root>/tex'), making the purpose understandable. It distinguishes from sibling 'formalize_tex' by indicating batch processing of all files rather than a single file, though it doesn't explicitly name the alternative. The description avoids tautology and provides specific scope information.

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 implies usage context through the project_root parameter and the 'all *.tex' scope, suggesting this is for batch processing of LaTeX files in a project. However, it doesn't explicitly state when to use this versus 'formalize_tex' or other siblings, nor does it provide prerequisites or exclusions. The guidance is functional but lacks explicit comparative direction.

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