NocturnusAI

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

With no annotations provided, the description carries the full burden and does well by explaining the tool's purpose, default behavior (global scope), and conflict resolution strategies. It clarifies that this is a mutation operation (merging/committing facts) and describes four specific behavioral outcomes based on the strategy parameter. However, it doesn't mention potential side effects like performance impact or error conditions.

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 efficiently structured in two sentences: the first states the purpose and default, the second explains the conflict strategies. Every word serves a purpose with no redundancy or fluff, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description does well by explaining the operation, defaults, and conflict behaviors. However, it doesn't describe what the tool returns (success/failure indicators, merged facts count, etc.) or potential error conditions, which would be helpful given the lack of output schema.

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 100%, so the schema already documents all three parameters. The description adds some value by explaining the default target scope ('global') and detailing the four conflict strategies with their semantics, but doesn't provide additional parameter context beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 clearly states the verb ('merge facts') and resource ('from one scope back into another'), with specific mention of committing hypothetical reasoning results to the main knowledge base. It distinguishes from siblings like 'fork_scope' (which likely creates scopes) and 'delete_scope' (which removes them).

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 provides clear context for when to use this tool ('to commit hypothetical reasoning results back into the main knowledge base') and mentions the default target scope. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the siblings (e.g., 'fork_scope' for creating scopes).

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