Athena MCP

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 effectively describes key traits: Athena 'only reasons and returns a concise response,' has 'NO tools,' and 'Does not modify files, run commands, or access the network beyond the reasoning call.' It also notes that 'You must gather relevant context yourself.' However, it lacks details on rate limits, authentication needs, or error handling, which would elevate it to a 5.

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 and front-loaded, with the first sentence stating the core purpose. Each subsequent sentence adds critical information without redundancy: usage context, limitations, and parameter guidance. There is zero waste, and the structure flows logically from general to specific details.

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 complexity (reasoning delegation with no output schema) and lack of annotations, the description is mostly complete. It covers purpose, usage, behavioral traits, and some parameter context. However, without an output schema, it doesn't detail return values or error formats, which is a minor gap. For a tool with no annotations and no output schema, this is strong but not perfect.

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 all four parameters thoroughly. The description adds minimal value beyond the schema, mentioning the 'context' arg briefly ('You must gather relevant context yourself and pass it in via the `context` arg.') but not explaining other parameters. This meets the baseline of 3 for high schema coverage, as the description doesn't significantly enhance parameter understanding.

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 tool's purpose: 'Ask Athena to think. Delegates deep reasoning to a stronger model when you hit a hard problem — architecture decisions, subtle bugs, plan critique, tricky logic.' It specifies the verb ('think', 'delegates deep reasoning') and resource ('Athena', 'stronger model'), and distinguishes it from alternatives by noting 'Athena has NO tools; she only reasons and returns a concise response.' With no sibling tools, this level of specificity is excellent.

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 provides explicit guidance on when to use this tool: 'when you hit a hard problem — architecture decisions, subtle bugs, plan critique, tricky logic.' It also clearly states when not to use it: 'Does not modify files, run commands, or access the network beyond the reasoning call.' With no sibling tools, this covers all necessary usage context, including exclusions and prerequisites like gathering context manually.

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