pythia-oracle-mcp

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

With no annotations provided, the description carries the full burden. It adds valuable domain context about what Events are and what data is returned (pricing, conditions, registry addresses), but omits operational details like authentication requirements, rate limits, or caching behavior that would help an agent understand invocation constraints.

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?

Three sentences with zero waste: sentence one establishes purpose, sentence two details specific return data justifying the 'overview' claim, and sentence three explains the domain concept. Information is front-loaded appropriately.

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 zero parameters and an output schema exists, the description is appropriately scoped. It helpfully lists the categories of data returned (pricing, conditions, stats) without needing to detail the full schema structure, though it could briefly clarify the relationship to sibling info-retrieval 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, establishing a baseline score of 4. The description appropriately does not fabricate parameter semantics where none exist, focusing instead on the tool's return value and purpose.

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 opens with a specific verb ('Get') and resource ('Pythia Events'), immediately clarifying scope. It distinguishes from siblings like 'get_events_guide' by specifying concrete returned data categories (pricing, registry addresses, subscription stats) rather than instructional content.

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 explains what Events are conceptually ('subscribe once and get notified when an indicator crosses a threshold'), implying the tool is for discovery before subscription. However, it lacks explicit guidance on when to use this versus 'get_events_guide' or 'subscribe_info', leaving the agent to infer based on the 'overview' label.

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