tomorrow_history

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

No annotations are provided, so the description must cover behavioral traits. It only states 'Get historical weather data' without disclosing rate limits, authentication requirements (though api_key parameter exists), data range limitations, or what the response contains. The description adds minimal behavioral context.

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 only 6 words, which is too brief. It lacks key information that would be necessary for an agent to use the tool correctly. Conciseness should not sacrifice completeness.

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?

With no output schema, the description should clarify the return format or structure of the historical data. It does not, and also fails to address parameter constraints or edge cases. The tool has 4 parameters and no output specification, making the description severely 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?

Schema description coverage is 0%, and the description does not explain any of the 4 parameters (location, startTime, endTime, api_key). It does not specify expected formats for dates, location, or how to obtain an API key.

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: to get historical weather data from Tomorrow.io. The verb 'Get' combined with 'historical' distinguishes it from siblings 'tomorrow_forecast' and 'tomorrow_realtime', which deal with forecast and realtime data.

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 implies the tool is for historical data but provides no explicit guidance on when to use it versus alternatives like 'tomorrow_forecast' or 'tomorrow_realtime'. No 'when not to use' or 'prerequisites' are mentioned.

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