Check Company Zone

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

Annotations already declare the tool as readOnly, non-destructive, idempotent, and open-world. The description adds that it returns a paginated JSON array with metadata, but there is a slight inconsistency between 'zone routing and web url' and 'Platform Services'. The description provides some behavioral context beyond annotations but is not fully transparent about the actual response shape.

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 three sentences long and covers purpose, usage, and pagination. It is concise but has some redundancy between the first sentence and the third. Could be slightly more streamlined.

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?

There is no output schema, so the description must explain what is returned. It mentions a paginated JSON array of Platform Services with metadata, which is adequate but lacks details about the fields within each service object. The mismatch between 'zone routing' and 'Platform Services' reduces completeness slightly.

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 100%, with clear descriptions for page and per_page including defaults and max. The description adds a note about controlling pagination and metadata, but this is mostly redundant with the schema. Baseline 3 is appropriate.

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's purpose: 'Get a response indicating zone routing and web url for zone' and 'read information about Platform Services from Procore'. It uses specific verb+resource and distinguishes from sibling tools like check_pdf_generation_status by referencing zone routing and Platform Services.

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 advises 'Use this to read information about Platform Services from Procore' and explains pagination control with page and per_page. While it doesn't explicitly mention when not to use or alternatives, the unique purpose and pagination guidance provide clear context for usage.

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