School MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully clarifies the categories of data returned (holidays, early releases, school events), but lacks information about error handling, authentication requirements, or behavior when no events exist for the specified month.

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 consists of two efficient sentences with no redundant information. The first sentence establishes the operation and scope, while the second clarifies the return value types, placing the most critical information first.

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 simplicity (two primitive parameters) and lack of output schema, the description adequately compensates by detailing the specific types of events returned. However, it could improve by noting error conditions or empty result behaviors.

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 both parameters ('Month number (1-12)' and '4-digit year'), establishing a baseline score. The description references the monthly scope ('for a given month') but does not add semantic meaning, validation rules, or examples beyond what the schema already 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 uses a specific verb ('Get') and resource ('school calendar events'), and clarifies the temporal scope ('for a given month'). It implicitly distinguishes from grade-related siblings by specifying event types like 'holidays' and 'early releases,' though it does not explicitly contrast with the sibling tool `get_schedule`.

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 provides no guidance on when to use this tool versus alternatives such as `get_schedule` (which may return daily class schedules versus monthly calendar events). There are no stated prerequisites or conditions that would help an agent decide between this and similar tools.

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