discover_dfg

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

No annotations provided, so description carries burden. Describes return value (handle for visualization + shape summary) but omits side effects, permissions, or performance characteristics. Adequate but could be more 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?

Two concise sentences, no superfluous content. Front-loads purpose and adds key output details efficiently.

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 one parameter and an output schema existing, the description covers core purpose and return behavior. Slight lack of context about prerequisites or relationship to sibling tools, but generally sufficient for a simple discovery tool.

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?

Only one parameter (log_id) with 0% schema description coverage. The description does not elaborate on the parameter's meaning, format, or role beyond its name. Provides no added value.

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?

Clearly states it discovers the directly-follows graph (DFG) of an event log. Distinguishes from sibling tools like visualize_dfg (rendering) and other discovery tools (Petri net, process tree, etc.). Verb+resource is specific.

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 explicit guidance on when to use vs. alternatives or prerequisites. Implies usage for DFG discovery but doesn't compare with other discovery tools or mention required prior steps (e.g., loading event log).

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