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

No annotations are provided. The description is minimal and does not disclose any behavior beyond the basic operation. For a simple mathematical function, this is adequate, but there is no elaboration on edge cases or return format (though output schema covers return values).

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 extremely concise, consisting of a single sentence with no wasted words. It efficiently conveys the tool's purpose.

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 presence of an output schema (though not shown), the description is complete enough for a simple mathematical tool. However, the description could slightly benefit from clarifying that it returns the nth triangular number for a positive integer, but it is sufficient.

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%, and the parameter 'n' has a description 'Which triangular number'. The tool description does not add any additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Get the nth triangular number' clearly states the action (get) and the resource (triangular number). It distinguishes this tool from siblings like nth_square, nth_cube, etc., by specifying 'triangular'.

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. There is no mention of when this tool is preferred over other nth-number tools or any prerequisites.

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