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

No annotations are provided, so the description must disclose behavioral traits. It mentions using SME but does not explain what happens during transfer (e.g., whether it modifies strategies, creates new ones, or returns a report). It also doesn't mention any prerequisites, side effects, or required permissions. This is a significant gap for a tool that potentially mutates state.

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, a single sentence with no fluff. It front-loads the core purpose and mechanism. It earns its place by being direct and informative, even if it lacks detail in other areas.

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 tool's complexity (cognitive analogical transfer via SME) and the lack of annotations, the description is insufficient. It does not explain the return value (output schema exists but description doesn't clarify), nor does it cover edge cases like what happens if the strategy_id is null. The agent lacks critical information about the transfer process and expected results.

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 only implies source and target structures but does not explain what each parameter means or how they are used. The optional strategy_id is completely unexplained, potentially causing agents to misuse it. The description fails to clarify parameter formats or selection criteria.

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 (transfer) and the resource (structural strategies) and specifies the mechanism (via Structure-Mapping Engine). It distinguishes itself from siblings like cognitive.compose_strategies by focusing on cross-domain transfer rather than composition. However, it could be more specific about the nature of the transfer (e.g., from one task structure to another) but the schema already hints at source and target.

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 provides no explicit guidance on when to use this tool versus alternatives. It implies usage for cross-domain strategy transfer but does not contrast with other tools like cognitive.report_transfer or cognitive.record_experience. An agent may infer from the name and sibling list, but clear exclusions would improve this.

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