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

With no annotations, the description must carry the full behavioral burden. 'Compute' implies a read-only operation, but the description does not disclose whether it mutates state, requires an existing lattice, handles a 'task' differently from a 'lattice', or what failure modes exist. No side effects, permissions, or return behavior are mentioned.

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 a single sentence with no wasted words, which is structurally concise. However, it is terse to the point of being jargon-heavy and omits essential context, so brevity comes at the cost of clarity.

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?

An output schema exists, so return-value documentation is not strictly required. But the tool is specialized, has no annotation safety profile, and has completely undocumented parameters; an agent still lacks the input semantics and selection criteria needed to call it correctly.

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%, and both parameters (task_data, lattice_id) lack descriptions in the schema. The tool description mentions 'lattice or task' but never explains the roles of the two parameters, whether they are alternatives or complements, or how lattice_id relates to task_data. An agent cannot determine what to pass.

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 states a specific verb ('Compute') and resource ('lattice or task') and adds a distinctive qualifier ('coordinate-free topological invariant signature'). It is clearly a computation tool, but it does not explicitly distinguish itself from siblings like compile_invariant_lattice or verify_lattice_transition, so an agent must infer the boundary.

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?

No guidance is given about when to use this tool versus its many siblings, particularly compile_invariant_lattice and verify_lattice_transition. There are no examples, prerequisites, or statements about which inputs are expected; the agent must guess from the name alone.

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