tempo_auth_status

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

No annotations are provided, so the description carries the full burden. It does disclose that it does not expose secrets, which is a useful behavioral safety note. However, it does not mention potential side effects (though there likely are none), error behavior, or whether it makes any network calls. The security disclaimer adds value, but for a tool with zero annotations, more explicit behavioral context would be expected.

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 short sentences, front-loaded with the core purpose ('Report whether optional subscriber authentication headers are configured') followed by a valuable safety qualifier ('Does not expose secrets'). Every word earns its place; no fluff.

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 no parameters and no output schema, the description provides the essential information an agent needs: what the tool reports and a critical security property. It is complete for a status-check tool, with no obvious gaps.

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 tool has zero parameters, so per the rubric the baseline is 4. The description does not need to add parameter meaning since there are none. It correctly focuses on the tool's purpose without unnecessary parameter discussion.

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 uses a specific verb 'Report' and a precise object 'whether optional subscriber authentication headers are configured for Tempo fetches.' It clearly states what the tool does and distinguishes itself from siblings like tempo_search and tempo_article, which perform different operations. Even without reading the schema, an agent can tell this is a status check.

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 no explicit guidance on when to use this tool versus the sibling tools. It implies it is a read-only status check, but does not state conditions for invocation, such as 'call this before attempting authenticated fetches' or 'use when you need to verify configuration.' Lacks any when-to-use or when-not-to-use context.

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