NocturnusAI

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

With no annotations provided, the description carries the full burden of behavioral disclosure and excels at this. It reveals critical behavioral traits: 'Non-transactional: each fact is attempted independently — contradictions are reported as errors without aborting the batch' and 'Returns counts of successful and failed assertions.' This provides essential information about error handling, atomicity, and output format that isn't available elsewhere.

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 perfectly sized and front-loaded. The first sentence states the core purpose, the second explains critical behavioral characteristics, and the third describes the return value. Every sentence earns its place with essential information, and there's zero wasted text or redundancy.

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 the complexity of a batch assertion tool with no annotations and no output schema, the description does an excellent job covering the essentials: purpose, behavioral characteristics (non-transactional nature, error handling), and return format. It doesn't explain authentication requirements, rate limits, or detailed error formats, but for a tool with 100% schema coverage and clear behavioral disclosure, it's nearly complete.

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 the single 'facts' parameter and its nested structure thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. However, it does provide context about how the parameter is used (batch processing for efficiency), which justifies the baseline score of 3.

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 tool's purpose: 'Assert multiple facts in a single call for efficiency.' It specifies the verb ('assert'), resource ('facts'), and distinguishes from potential siblings by emphasizing batch processing efficiency. The description goes beyond the name/title to explain the core functionality.

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: 'for efficiency' when needing to assert multiple facts. It implicitly suggests using single-fact alternatives for simpler cases but doesn't explicitly name alternatives or state when NOT to use this tool. The guidance is helpful but not comprehensive about trade-offs.

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