scorecard_query

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

The annotation readOnlyHint=true already covers safety, and the description adds useful context about filter syntax and range operations. Beyond that, it doesn't disclose additional behaviors like pagination, default limits, or response structure, but given the annotation coverage, a score of 3 is appropriate.

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 concise and well-structured: a one-sentence main description followed by four focused, annotated examples. Every element earns its place, with no redundant information or filler.

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 and the absence of an output schema, the description addresses the core query syntax thoroughly. It would benefit from a brief note on the return format or expected response, but the current examples and schema together provide a solid foundation for invoking the tool correctly.

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 schema already covers all parameters with descriptions and examples for filters and sort. The description adds significant value by providing four additional filter examples demonstrating the __range suffix and exact-match syntax, which clarifies how to construct complex queries beyond the schema's single example.

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 it's an 'Advanced College Scorecard query' with custom field filters and ranges, which conveys the tool's purpose and scope. The 'Advanced' label and filter examples distinguish it from sibling tools like scorecard_search and scorecard_compare, though it doesn't explicitly name them.

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 implies usage for advanced querying via filter examples, showing when to use range and equality filters. However, it does not explicitly state when to prefer this tool over siblings or provide exclusions, leaving usage guidance mostly implied.

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