check_diagram_equivalence

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

With no annotations, the description carries the full behavioral burden, and it says almost nothing beyond the return type. It does not state that this is a side-effect-free read, nor warn about the potentially expensive nature of isomorphism checking, nor clarify that it does not mutate either diagram.

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?

Short and front-loaded: the purpose sentence comes first, followed by a compact Args/Returns block with no filler. Slightly formulaic but nothing wasted.

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 the terse 'Returns: dict with equivalence status' is acceptable. For a two-parameter tool the core is covered, but the absence of any usage or behavioral context leaves gaps relative to the richer sibling set it sits in.

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, yet 'First diagram ID' and 'Second diagram ID' merely restate the schema titles. It adds no format, source, or constraint information (e.g., where IDs come from, whether they must be loaded first via diagram_load).

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 and resource ('Check if two diagrams are structurally equivalent') and adds the parenthetical '(isomorphic)' to disambiguate what 'equivalent' means. It does not, however, distinguish itself from the sibling explore_equivalent_states, leaving the agent to 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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative explore_equivalent_states. The agent must guess whether this is a pairwise comparison tool or a broader exploration tool.

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