addprimes

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

The description alone suggests solely additive behavior, but the parameter description reveals the tool can also retrieve the current list when given None. This dual behavior is not disclosed in the main description, and no side effects or error conditions are mentioned. With no annotations to fill gaps, the description is insufficient.

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 a single sentence, but it fails to front-load the dual retrieval functionality. It could be more efficient by explicitly stating both uses.

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?

Even though there is an output schema (not shown), the tool's behavior is more complex than adding primes; it also retrieves. The description does not address error conditions or what happens with duplicate primes. Given the dual functionality and lack of annotations, the description is incomplete.

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 input schema has 100% description coverage for its one parameter. The parameter description adds significant meaning beyond the schema by clarifying that passing None returns the current list, which explains the optionality.

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 specifies the action 'add' and the target 'factorisation table', making the tool's purpose clear. However, it does not distinguish from sibling tools like 'removeprimes' or 'init_primes'.

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 guidance is provided on when to use this tool versus alternatives such as 'init_primes' or 'removeprimes'. There is no mention of prerequisites or appropriate contexts for adding primes.

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