SimpleFunctions

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

No annotations provided, so description carries full burden. It successfully discloses 'Read-only, no auth' (critical safety info) and hints at return content (prices, volume, metadata). Minor gap on rate limits or error handling, but covers essential behavioral traits well.

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?

Two sentences, zero waste. First sentence establishes function and safety properties; second provides usage guidelines. Perfectly front-loaded and structured.

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 2-parameter read-only list tool, description is comprehensive. Compensates for missing annotations with safety disclosures, hints at return structure despite no output schema, and provides clear usage context. Minor room for pagination or rate limit 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%, documenting topic values and limit constraints. Description adds no parameter-specific details, which is acceptable per rubric baseline of 3 when schema coverage is high.

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?

Specific verb ('List') + resource ('live prediction market contracts') with clear scope (YES/NO prices, 24h volume, metadata). Distinguishes from siblings by contrasting with search_markets and get_context.

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?

Explicit guidance: 'Use for deep dives on a specific topic' and clear alternatives named ('use search_markets if you have a keyword... or get_context for a high-level overview'). Perfect sibling differentiation.

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