state_education

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

The readOnlyHint annotation already states this is a safe read operation. The description adds context about the type of data (education metrics) and available filters, but does not disclose return format, pagination limits, or other behavioral traits beyond the schema.

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, front-loaded with the core purpose, then supported by examples and filter options. Every sentence earns its place with no fluff or repetition.

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?

With no output schema and a generic description, the tool does not fully specify what the response contains or how results are structured. The described data categories give a broad idea, but the absence of return format details and the minimal guidance on SoQL usage make it less complete than it could be.

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 input schema has 100% description coverage for all 6 parameters, so the schema already explains each parameter well. The description reinforces filtering by county, year, or keyword, but adds no new parameter-specific meaning beyond what the schema provides.

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 queries education data for a US state, with concrete examples like school enrollment, assessment scores, graduation rates, and demographics. This distinguishes it from sibling tools like state_crime, state_health, and other state_* services.

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?

Usage is implied by the domain (education data for a US state) and the available filters (county, year, keyword). However, it does not explicitly say when to use this instead of other education-related tools or state_* sibling tools, nor does it mention any exclusions or alternatives.

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