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' (safety), 'no auth' (permissions), 'no parameters' (input constraints), and ranking methodology ('absolute probability change'). Lacks rate limits or caching details, but covers core behavioral traits.

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: first defines function and scope, second states constraints/annotations-equivalent info, third provides usage guidelines. Front-loaded with the most critical information (what it returns).

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 simple read-only tool with no output schema, description adequately explains the conceptual return (ranked movers) and temporal scope (24h). Sibling tool references provide necessary context for correct selection. Could benefit from hint about return structure (list count/format), but sufficient for complexity level.

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?

Zero parameters present (empty schema). Per scoring rules, 0 params establishes baseline of 4. Description confirms 'no parameters', aligning with schema and reinforcing the parameter-free nature of the tool.

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?

Description uses specific verb 'Top' (implying retrieve/list) with specific resource 'price movers across all prediction markets', scoped to '24h' and ranked by 'absolute probability change'. Explicitly distinguishes from siblings get_world_delta and get_context by contrasting use cases.

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?

Provides explicit when-to-use guidance ('Use this when you need "what moved today"') and names specific alternatives for related use cases ('use get_world_delta for... diff against an arbitrary timestamp, or get_context for movers bundled with edges'). Clear differentiation between tools.

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