search_campuses

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

Annotations already declare readOnly/idempotent/destructive hints; the description adds valuable behavioral context about pagination (cursor/next_cursor), total_matches via include_total, response structure (payload.table, payload.exports), and follow-up via next_tool_call when completeness or pagination flags are set.

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 detailed but every sentence provides operational value: search filters, examples, tool distinction, pagination, response structure, and follow-up handling. It is appropriately proportioned to the tool's complexity, though slightly longer than the minimal ideal.

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 8 optional params and no output schema, the description covers essential aspects: what the tool returns (basic info, payload.table, payload.exports), pagination behavior, and when follow-up is needed. It fully equips an agent to invoke and interpret results correctly.

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 75%, so the description compensates by explaining filter semantics with concrete examples (IDEA, KIPP, Austin ISD), clarifying cursor as a skip offset, and describing meta_fields and include_total, adding meaning beyond the schema.

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 searches campuses by name/number/district with filters for status, rating, and grade_level, and explicitly distinguishes it from get_campus_detail by noting it returns basic info for identifier fetching before detail/compare/map calls.

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 explicit when-to-use guidance: use this to fetch identifiers before detail/compare/map calls, and use get_campus_detail for full stats. Also explains pagination usage, include_total, and meta_fields, giving clear context for alternatives.

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