Build Knowledge Graph

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

Discloses async operation and task_id return, which are not in annotations. Annotations already indicate non-read-only, non-destructive, non-idempotent, so description adds value with polling behavior.

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 sentences, direct, no filler. Front-loaded with main action.

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?

Provides essential async polling info and scope. Missing details about prerequisites are in schema; output schema absent but return type is mentioned.

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 descriptions cover all 5 parameters (100% coverage), so description adds little beyond noting documents/ontology context. Baseline 3 applies.

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?

Clear verb 'Build' with specific resource 'knowledge graph' from project documents and ontology. Distinguishes from sibling tools like get_graph_data (retrieval) and delete_graph (deletion).

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?

Explicitly states async behavior and how to poll with mirofish_get_task, giving clear usage context. Does not mention alternatives or prerequisites, but the schema covers the ontology prerequisite.

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