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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that the tool computes a signature. It does not disclose side effects, input requirements, error behavior, or what happens when both optional parameters are null. It is not misleading, but it is far too thin to be transparent.

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 front-loaded sentence with no filler or redundancy. It is concise and readable, though terseness comes at the cost of missing critical usage and parameter context.

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 large sibling list, a nearly identical sibling tool name, and no annotations, the description is not complete enough for an agent to confidently select and invoke this tool. The output schema exists, but input semantics, selection criteria, and behavioral expectations are absent.

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 for undocumented parameters. 'Lattice or task' loosely maps to lattice_id and task_data, but it does not explain whether one is required, how they interact, or what constitutes valid data. The optional-by-default nature of both parameters is left unexplained.

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 action ('compute') and a specific resource ('coordinate-free topological invariant signature of a lattice or task'). The qualifier 'coordinate-free' hints at a distinction from the sibling compute_lattice_signature, but the description does not explicitly differentiate them.

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 the closely named sibling cognitive.compute_lattice_signature or related lattice tools such as compile_invariant_lattice. There is no mention of required inputs, prerequisites, or alternative selection criteria.

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