list_school_features

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

Describes that it parses sidebar navigation and returns a list of sections, implying read-only. No annotations exist, but description discloses the mechanism. Lacks mention of error handling or edge cases, but overall transparent.

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?

Concise: two short paragraphs with a clear summary and an Args section. No redundant or filler words.

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 simple tool with one parameter and an output schema, the description explains return type and examples. Could mention behavior on invalid IDs, but output schema likely covers that.

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?

Single parameter 'school_id' is explained with instruction to use list_schools to find IDs, adding significant value beyond the schema's integer type. Schema coverage is 0%, so description fully compensates.

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 the tool lists features for a school by parsing sidebar navigation, and gives examples of returned sections. It distinguishes from sibling 'list_schools' which lists schools, not features.

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 guidance on when to use (to see available features per school) and references list_schools to obtain school_id. Does not explicitly state when not to use, but alternatives are clear from sibling tools.

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