get_district_schools

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

With no annotations, the description carries the burden of behavioral disclosure. It specifies the parameter format (7-digit NCES LEA ID) but lacks details on pagination, response format, error behavior, or school type scope (e.g., public vs all). This is minimal for a tool with no annotation support.

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 two sentences and front-loaded: the purpose is stated immediately, followed by a concise parameter explanation. No filler or redundancy.

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?

This is a simple list tool with one parameter and no output schema, so the description is adequate but not complete. It does not explain what the response looks like (e.g., list of school objects) or whether pagination applies. Given the low complexity, a 3 is appropriate.

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 only defines nces_id as a string with no description, but the tool description adds crucial meaning: '7-digit NCES LEA ID of the district'. This compensates for the 0% schema coverage and fully explains the required parameter.

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 'List all schools in a district' with a specific verb (List) and resource (schools). It distinguishes itself from sibling tools like get_school (single school) and find_schools_near_address (location-based).

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 when you have a district NCES ID and want its schools, but it does not explicitly mention alternatives or when not to use this tool. No exclusions are stated, so the context is clear but not fully guiding.

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