tempo_article

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

No annotations are provided, so the description must disclose behavior. It states the tool fetches and returns data, implying a read-only operation, but does not explicitly state whether it is safe, requires authentication (given the presence of tempo_auth_status), or has any side effects or limitations (e.g., only public articles). This lack of behavioral disclosure is a gap.

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 sentences with no filler. The first sentence states the function, and the second gives a clear usage directive. Information is front-loaded and every word is purposeful.

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?

The tool is relatively simple (one required param) and the description covers the main purpose and a usage hint. However, it lacks an output schema and does not mention behavioral constraints like authentication (despite the existence of tempo_auth_status), error handling, or any caveats about availability of public articles. An agent might not know if it needs to call tempo_auth_status first or what specific metadata fields to expect. So it is adequate 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 input schema already describes the url and include_media parameters, providing 67% coverage. The description adds a general sense of the output ('clean text plus normalized metadata') but does not elaborate on the parameters beyond what the schema provides. The include_body parameter lacks a schema description, and the tool description doesn't compensate for that either. Minimal added value over the schema.

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 ('Fetch'), a specific resource ('one public Tempo.co article'), and the output ('clean text plus normalized metadata'). It also hints at a relationship with 'deep insight' (likely tempo_insights), which helps disambiguate from siblings.

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 explicitly says 'Use this before requesting a deep insight for a particular URL', which tells the agent when to use this tool relative to tempo_insights. It does not list other alternatives like tempo_search or tempo_compare, but it provides clear usage context for the primary workflow.

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