get_offices

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

With no annotations provided, the description carries the full burden. It discloses a limit ('up to 1000'), a permission tier ('readonly-owner'), and the underlying HTTP method, but it does not describe the exact return structure, handling of invalid IDs, or behavior when exceeding the limit. This partial disclosure is helpful but not comprehensive.

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 that front-loads the primary action and resource. The additional notation about HTTP mapping and tier is compact and useful, with no wasted 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 bulk retrieval tool with one parameter and no output schema, the description covers the essential aspects: purpose, parameter meaning, limits, and permission scope. It lacks explicit usage guidance and return format details, but given the low complexity, it is largely complete.

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 schema only defines officeIDs as an array of numbers with no description. The description adds crucial meaning by identifying them as 'office IDs' and specifying a maximum count of 1000. This goes beyond the schema, though it does not cover other constraints like uniqueness or minimum size.

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 action ('Get full office records'), the resource ('office records'), and the scope ('up to 1000 office IDs'). This distinctly differentiates it from sibling tools like search_offices, which imply a search operation rather than bulk retrieval by known IDs.

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 usage context is implied: use when you have a list of up to 1000 office IDs and want complete records. However, there is no explicit mention of when not to use it or reference to alternative tools like search_offices, which leaves the guidance to inference.

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