The AGI-2027 Thesis Tracker: a single auditable 0-100 score of how much of Aschenbrenner's Situational Awareness thesis is holding up, with method and full score history.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the return content (score, method, history) but omits potential behavioral details like data freshness, error conditions, or whether any side effects occur. For a simple no-parameter getter, this is adequate but not rich.
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, well-structured sentence that front-loads the key information (what it is, what it returns) and includes useful qualifiers (auditable, method, full score history). No wasted words.
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's simplicity—no parameters, no output schema—the description is complete. It explains the purpose, the output type, and the additional content (method and history), which fully addresses what an agent needs to invoke it.
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 no parameter semantics are needed. The baseline for 0 parameters is 4, and the description correctly avoids adding irrelevant parameter information.
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 what the tool does: retrieve a single auditable 0-100 score for Aschenbrenner's Situational Awareness thesis, along with method and history. It is specific enough to distinguish from sibling tools by naming the exact tracker subject, though it does not explicitly differentiate 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?
There is no explicit guidance on when to use this tool versus alternatives, but the description implies it is the authoritative source for thesis status. The sibling names suggest related trackers, but the description does not state any exclusions or alternative choices.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect: market-call ledger, thesis score, prediction verdicts, and site search. No overlap in purpose or output.
Three of four tools follow the get_ prefix pattern, but search_site deviates by using a bare verb_noun form. Still mostly consistent and predictable.
Four tools is well-scoped for an informational read-only server covering a niche site. Each tool earns its place without redundancy.
Covers the core data sets (track record, thesis, verdicts) and site search. Minor gap: no direct tool for other content types (e.g., articles), but search mitigates this.