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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds that the default engine is set at project creation, but it never says whether changing the engine recompiles or invalidates existing outputs, or whether the change applies only to future builds — a real gap for a project-level mutation.

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?

Three sentences, purpose front-loaded, then value-selection rules, then usage trigger. No filler; each sentence carries information the agent needs to act correctly.

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?

For a two-required-param, no-output-schema tool with full schema coverage, the description covers purpose, value choice and trigger. Only the post-change effect (recompilation/regeneration of output) is unstated, which is a minor but real omission.

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 coverage is 100%, so the baseline is 3, and the description goes beyond it by giving decision criteria for the enum-less 'compiler' string (which LaTeX packages/document features require which engine). project_id is left to the schema, which is fine since it is self-describing.

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?

States a specific verb+resource ('Set the TeX engine a project builds with') and immediately enumerates the three legal values. It also implicitly separates itself from create_project by noting 'letX picks an engine when a project is created', so an agent can distinguish it from the sibling that creates projects.

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?

Gives an explicit trigger ('Use when the user asks for a different engine or the document needs one') plus per-document routing rules: fontspec/unicode-math/polyglossia/xeCJK need xelatex or lualatex, and \directlua/luacode needs lualatex. That is more than context — it tells the agent which value to select and why.

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