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

With no annotations, the description must carry all behavioral disclosure, but 'bundle' only vaguely suggests aggregated output. Nothing is said about scope, return structure, or distinctions like nearby vs. catchment schools, leaving behavior almost entirely 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?

The description is extremely short and empty of informative content. This is under-specification rather than effective conciseness; no sentence earns its place because no useful information is provided.

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?

The tool sits among many school-related tools, but the description gives no context on scope, output semantics, or how it relates to other sibling endpoints. Even though an output schema exists, an agent cannot infer what 'all schools' means or how it is bundled.

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 0% and the description provides no explanation of the suburb_name parameter beyond its type in the schema. There is no added meaning about expected format, validation, or purpose, despite the parameter being required.

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 'All schools — bundle' essentially restates the tool name's 'schools_all' without a clear verb or resource. It hints at a broad school dataset but does not indicate what action the tool performs or how it differs from siblings like suburbs_schools_catchment or properties_schools_all.

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?

No guidance is given about when to use this tool versus any of the numerous school-related siblings. There are no exclusions, alternatives, or context signals to help an agent select it correctly.

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