Calculation History

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

Annotations are empty, so the description must disclose behavior. It only states 'Get calculation history', which implies a read operation but does not explicitly confirm safety or mention any side effects, authentication needs, or potential limitations. This is insufficient for a tool with no annotation support.

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 short (one sentence) but lacks substance. While it is concise, it does not earn its place with meaningful content; it is closer to under-specification than efficient communication.

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?

Despite having an output schema and a single optional parameter, the description fails to provide context about what constitutes 'calculation history' or how it relates to sessions or users. Important for a tool that could be ambiguous among many siblings, but left unaddressed.

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 coverage is 100%, so the schema already documents the 'limit' parameter with a default and description. The tool description adds no extra information about the parameter's purpose or constraints beyond what the schema provides, meeting the baseline but not exceeding it.

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 calculation history' provides a verb+resource combination that is clear in a basic sense, but it lacks specificity about the scope or context of the history (e.g., per session, global). It distinguishes itself from siblings like clear_history, but not strongly.

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 session_calculate or clear_history. The description does not mention any conditions or preferences, leaving the agent with no help in choosing between similar tools.

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