parse_er_diagram

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. It states the parse/extract action but does not reveal whether the extracted schema is persisted, whether it overwrites an existing schema, whether a connection must be active, or what the actual return value is. For a tool sitting among schema-management siblings, this is a meaningful transparency gap.

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 direct sentence with the action and output front-loaded and no filler. It earns a 4 for efficiency, though it stops short of 5 because the terseness omits usage and behavioral context that would make it genuinely more useful.

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?

With no annotations and no output schema, the description needs to explain what happens on invocation and what the caller receives. It names the extracted components (entities, attributes, relationships) but omits side effects, persistence behavior, return format, and how this relates to sibling tools. This is insufficient for an agent deciding between parse_er_diagram, validate_diagram, and list_entities.

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?

The input schema has 100% coverage for the single optional 'diagram' parameter, including the fallback to the configured diagram source. The tool description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 names a specific action ('Parse'), a specific input type ('Mermaid ER diagram'), and a concrete outcome ('extract the complete database schema including entities, attributes, and relationships'). This clearly distinguishes it from sibling tools that list, validate, or generate rather than parse and extract.

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 implies the tool is the entry point for loading a schema from a diagram, but it gives no explicit guidance about when to prefer it over validate_diagram, list_entities, or generate_sql. There is no mention of prerequisites, ordering, or exclusions, so the agent must infer usage context.

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