get_analysis_archive_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 of behavioral disclosure. It offers domain terms like 'immutable analysis' and 'append-only outcome' but does not state whether the call is read-only, what kind of status payload is returned, or whether there are any side effects or dependencies.

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 a single compact line with no filler, and it front-loads the resource and operation. It is slightly cryptic due to mixed language and jargon, but it earns its place by conveying the key conceptual categories succinctly.

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 lack of an output schema, the absence of annotations, and a large sibling set, the description is too sparse to fully orient an agent. It does not specify what status data is returned, whether the status is a snapshot or live, or how this tool differs from similar archive/status tools.

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 and an empty schema, so there are no parameter details for the description to clarify. The baseline of 4 applies because nothing is left undocumented.

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 identifies the resource ('Analysis Archive') and the operation ('Status'), and adds specific aspects (immutable analysis, append-only outcome, reanalysis) that go beyond the bare tool name. However, it does not explicitly contrast with nearby status tools like get_forward_test_status or get_data_source_status, so differentiation is implied rather than stated.

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?

There is no guidance on when to use this tool versus any of the many sibling tools, nor any context about what conditions warrant calling it. The only usage signal is the tool name itself, which 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.