tempo_search

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

With no annotations provided, the description carries the full burden. It discloses that results are 'candidates' with specific fields, but it does not mention potential side effects (e.g., read-only nature), authentication requirements (given sibling tempo_auth_status exists), or pagination/result limits beyond the schema. It provides some behavioral context but leaves gaps.

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 two sentences, clear, and front-loaded with the main purpose. It avoids redundancy and includes only relevant information about what is returned. No filler or excessive detail.

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?

For a simple search tool, the description covers the query and return fields, but it lacks critical context such as authentication prerequisites (sibling tempo_auth_status implies auth may be needed) and any pagination or limit behavior. It does not mention sorting or how results are ordered, which an agent might need to know. Essential enough to score a 3, but not complete.

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 schema covers 'query' with a description, but 'limit' has no description and the tool description does not mention either parameter. The description adds no value beyond the schema for the query parameter and fails to compensate for the undocumented limit parameter. Since schema coverage is 50% (not low, but not high), the description should at least reference the limit behavior; it does not.

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 states a specific verb ('Search'), resource ('Tempo.co reporting'), and what it returns (article candidates with fields). It clearly distinguishes from siblings like tempo_article (likely retrieval of a specific article) and tempo_insights (likely analysis), so an agent can tell it apart without inspecting other tools.

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 usage when you have a query, but it does not explicitly mention when to use this tool versus alternatives. Sibling names suggest tempo_article is for specific article retrieval, but the description does not state 'use tempo_article when you have a direct URL' or similar exclusions. Guidance is implicit rather than explicit.

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