School MCP

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

No annotations provided, so description carries full burden. Discloses return structure ('Returns all courses with their assignments and scores') and temporal indexing behavior. Does not mention safety properties (read-only) or error conditions, though 'Get' in name strongly implies read-only behavior.

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 zero waste: purpose statement, return value disclosure, and parameter usage guidance. Front-loaded with core action and appropriately sized for the tool's simplicity.

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?

Complete for a single-parameter read tool with no output schema. Covers purpose, return payload structure, and parameter usage. Minor gap: does not describe error behavior for invalid reporting periods or auth requirements, though these may be implicitly understood in context.

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?

Schema coverage is 100%, establishing baseline 3. Description adds valuable imperative usage context ('Use reportingPeriod 0 for the current period. Increment for previous periods.') that clarifies the indexing semantics beyond the schema's mechanical description.

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?

Specific verb ('Get') + resource ('full gradebook') + scope ('for a reporting period'). Effectively distinguishes from siblings like 'get_grade_summary' and 'get_grade_details' by emphasizing 'full' scope and 'all courses with their assignments and scores'.

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 parameter usage logic (0=current, increment for previous) but lacks explicit guidance on when to choose this over siblings like 'get_grade_summary' or 'get_failing_or_low_grades'. Differentiation is implied through 'full' but not stated directly.

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