list_schools

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

No annotations are present, so the description must carry the behavioral burden. It discloses an important behavior: returns JSON containing schools, students, and the user ID, which helps an agent know what to expect. However, it does not mention pagination, filtering, or potential failure modes, leaving some behavior opaque.

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 no filler; the main action and output format are front-loaded. The get_directory pointer is a routing hint that earns its place without bloating the description.

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 zero-parameter listing tool, the description covers purpose, output contents, and next-step usage. Since an output schema exists and this is a simple operation, nothing critical for invoking it correctly is missing.

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 tool has zero parameters, so schema coverage is trivially complete and the baseline is 4. The description adds value by explaining that the output values, school_id and student_id, are meant to be consumed as inputs by other tools.

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?

States a specific verb and resource: lists schools and students in the ParentSquare account. This clearly identifies the tool's function, though it does not explicitly differentiate it from siblings like list_students or list_class_students.

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 clear context: use the returned school_id and student_id in other tools, and use get_directory for contact info. It lacks explicit when-not-to-use guidance relative to list_students or list_class_students, but the pointers are actionable.

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