tempo_compare

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

With no annotations provided, the description carries the full burden. It describes what the comparison highlights, which is useful, but does not disclose any constraints like authentication requirements, potential latency, or failure modes. The tool appears to be read-only, but this is not explicitly stated. It is not misleading but lacks depth on behavioral traits.

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?

Two concise sentences with no fluff. The core purpose is front-loaded, followed by a use-case example. Every word earns its place.

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 tool has 2 parameters, no output schema, and no annotations, the description covers purpose, range, and use case, but omits details about the focus parameter and any prerequisites (e.g., whether URLs must be publicly accessible). An agent could likely call the tool correctly but might not understand the full scope of the focus lens or output format.

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 50%; the focus parameter's description ('Optional comparison lens') is vague. The tool description clarifies that the urls parameter should contain article URLs, but it does not elaborate on the focus parameter or its possible values. It adds some meaning to urls but falls short of compensating for the gap on focus.

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 verb ('Compare'), the resource ('Tempo.co articles'), and the scope (2–5 articles). It also lists specific outputs (shared entities, repeated facts, framing, chronology, gaps) and is distinct from sibling tools that search, fetch single articles, or provide insights.

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 gives clear context with 'Useful for tracking a developing story' but does not explicitly contrast with alternatives like tempo_search or tempo_insights. It implies use when multiple articles exist for comparison, but lacks explicit exclusion criteria or mentions of alternative conditions. Slightly above baseline.

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