propline_get_scores

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

No annotations, so description carries full burden. Discloses Free-tier nature (suggests rate limits) and returned data types. However, does not specify how recent data is, max results, or if any side effects exist. Adequate but not rich.

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 concise sentences plus a usage quote. Front-loaded with main purpose. No unnecessary words. Excellent structure.

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 simplicity (2 params, no output schema), the description covers purpose and usage adequately. Could mention pagination or limits, but not essential for typical use. Slightly incomplete regarding 'recent' definition.

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 50% (only days_from documented). Description adds context that tool returns 'recent and live' scores, but does not elaborate on sport_key format or usage beyond the schema. Adequate but not exceptional.

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?

Clearly states it returns recent and live game scores plus status for a sport. Verb 'returns' and resource 'scores and status' are specific. Distinguished from siblings like 'propline_get_event_results' by focusing on live scores.

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 a concrete use case ('is this game over yet, what was the final score') that helps agent select tool. However, no explicit when-not-to-use or alternatives given, but context is clear enough.

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