AI Takeover Tracker MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what information is returned (score, risk tier, etc.) and mentions the existence of a more detailed external report, which adds useful context. However, it doesn't disclose rate limits, authentication requirements, data freshness, or error conditions that would be important for an agent to know.

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 appropriately sized with two sentences. The first sentence efficiently states the purpose and outputs. The second sentence adds valuable context about the external report without being redundant. There's no wasted language, though it could be slightly more structured for optimal agent comprehension.

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 tool with no annotations and no output schema, the description provides good information about what data is returned. However, it doesn't specify the format or structure of the return values (e.g., whether it's a JSON object with specific fields), which would be important for an agent to process the results correctly. The mention of the external report adds context but doesn't fully compensate for the lack of output details.

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?

Schema description coverage is 100%, so the schema already documents the 'identifier' parameter thoroughly. The description doesn't add any additional parameter information beyond what's in the schema, but since there's only one parameter and it's well-documented in the schema, the baseline of 3 is appropriate. The description's clarity about what the tool returns provides good context for parameter usage.

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 the specific action ('Get AI displacement risk for a specific occupation') and lists the exact outputs (score, risk tier, protective factors, labor data, displacement timeline). It distinguishes from siblings like 'get_occupation_tasks' or 'search_occupations' by focusing on risk assessment rather than task lists or search functionality.

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 by mentioning it provides a 'summary' and that a 'full interactive report' exists elsewhere, suggesting this is for quick overviews. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_latest_score' or 'search_occupations', nor does it provide clear exclusions or prerequisites for usage.

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