获取北邮校区信息

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 discloses the output (campus IDs and main buildings) and its purpose, but does not mention aspects like authentication needs, data freshness, error behavior, or that it is a static list. This is adequate for a simple parameterless tool but lacks depth.

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 a single, well-structured sentence in Chinese that is concise (~25 characters) and front-loaded with the main action. Every phrase adds value: the specific campuses, their IDs, and the use case.

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 description explains what the tool returns (campuses and main teaching buildings) and why (for campus_id selection). However, it does not specify the return format (e.g., list of objects) or whether buildings are included in the same response. For a simple tool without an output schema, this is mostly complete but has a minor gap.

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 no parameters, and schema description coverage is 100%. The description implicitly confirms no inputs are needed. Per guidelines, zero parameters receive a baseline score of 4.

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 returns the two campuses (Xitucheng 01, Shahe 04) and their main teaching buildings, with the explicit purpose of selecting campus_id for classroom queries. This distinguishes it from siblings like get_classrooms, which likely returns classrooms for a given campus.

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 directly states this tool is 'used for selecting campus_id when querying available classrooms,' providing clear context for when to use it. However, it does not explicitly mention when not to use it or cite alternatives among siblings, leaving some implicit guidance.

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