Import Issues

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

Annotations already convey that this is not read-only and not destructive. The description adds source/destination context but does not disclose important behavior such as whether imports merge or replace existing nodes, how duplicates are handled, or whether any mapping/configuration is required.

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?

A single, front-loaded sentence that states exactly what the tool does with no filler or redundant detail.

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 that this is a mutating tool with no output schema and external integrations, the description is too sparse. It omits return behavior, side effects on existing graph data, prerequisites, and any merge/overwrite semantics, so an agent cannot fully predict the outcome.

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 schema documents only the optional 'project' param; the required 'issues' array is completely opaque. The description names external sources but does not specify the expected structure or fields of each issue object, leaving a critical gap for correct invocation.

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?

Uses a specific verb ('import') with a clear resource ('external issue tracker issues') and destination ('state graph memory'). Distinguishes well from siblings like export_issues (reverse operation) and import_graph (graph-level import).

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 when to use the tool: for bringing GitHub/Jira issues into the graph. It does not explicitly state when not to use it or name alternatives, but the context is reasonably clear given the sibling set.

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