查询办公场所

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

With no annotations, the description carries the full burden. It discloses that the tool returns office ID, name, address, and organization, and supports filtering. However, it does not mention pagination behavior (size/current parameters), which is a significant behavioral trait for a list API. The schema covers the parameters but the description could have added more context.

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 sentence, front-loaded with the main purpose, then specifies filtering capabilities and return fields. Every word is useful with no redundancy.

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 provides the essential purpose, filtering options, and return fields, which is largely sufficient for a list/search tool. It omits explicit mention of pagination parameters, but the schema already documents them, and the output schema is absent but return fields are described. 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?

Schema description coverage is 100%, so the baseline is 3. The description adds that filtering is possible by name and address, aligning with officenm and address parameters, but does not explain the pagination parameters (size, current) meaning. Thus it adds minimal semantics 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 queries the office list on the specific Shangang Capital Digital Office Platform, using a specific verb '查询' and specific resource '办公场所列表'. It distinguishes from sibling tools by focusing on offices rather than rooms and list versus detail operations.

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 clearly conveys when to use this tool: when searching/filtering office locations by name or address. It does not explicitly exclude other tools like get_office_detail for details, but the context makes the general usage pattern obvious.

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