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 states the tool 'discovers' and 'transduces', implying a read/compute operation, but it does not disclose whether this mutates state, whether it requires a pre-existing source_lattice_id, what happens when inputs are missing, or what the output contains. The abstract phrasing leaves the tool's actual behavior opaque.

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 and technically concise, but it is dense with abstract jargon and lacks any structural breakdown. It earns its place as a one-line summary, but the phrasing is not accessible or informative enough to be considered well-structured for an agent.

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?

Despite having an output schema, the description does not explain what the tool returns, how the step_budget affects behavior, or what inputs are required for a successful call. The abstract language and lack of usage context make the definition incomplete for an agent deciding whether and how to invoke it.

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 the four parameters, but it does not. The terms 'source_lattice_id' and 'target_lattice_id' are not explained, and the relationship between 'target_task_data' and the lattice IDs is unclear. The description's mention of 'source experience' and 'target problem' loosely maps to the parameters but adds no concrete meaning about formats, defaults, or how the parameters interact.

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 uses a specific verb ('Discover') and names the resource ('topological homomorphism between source experience and target problem'), so it conveys the core function. However, the phrasing is highly abstract and jargon-heavy ('topological homomorphism', 'transducing solution paths'), and it does not clearly distinguish this from the closely named sibling cognitive.analogical_transfer, which likely performs a similar mapping role. An agent would struggle to know what concrete operation is being invoked.

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 alternatives such as cognitive.analogical_transfer, cognitive.few_shot_induce, or cognitive.report_transfer. The description implies a use case (transferring solutions from a source to a target) but provides no conditions, prerequisites, or exclusions. An agent has no basis for selecting this tool over its siblings.

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