Show Rounding Configuration

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

Annotations indicate a safe, idempotent read operation, but the description introduces contradictory behavior: a paginated JSON array of Field Productivity records. The actual endpoint likely returns a single rounding configuration object. This contradiction undermines transparency and could lead to incorrect tool invocation.

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 verbose and includes irrelevant details about Field Productivity records and a Procore API category. It lacks front-loading of essential information and contains redundant or contradictory statements. Every sentence does not earn its place.

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 read tool with no output schema, the description should clearly state what is returned. Instead, it falsely claims a paginated array of Field Productivity records. The actual rounding configuration behavior and response format are not described, leaving the agent underinformed. The description is incomplete and misleading.

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 fully covers the three parameters (company_id, page, per_page) with basic descriptions. The description adds pagination context but also introduces extraneous and misleading information about Field Productivity records, which does not align with the actual parameters or endpoint. It does not provide meaningful additional semantics.

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 attempts to describe both rounding configuration and Field Productivity records, creating confusion. The title and endpoint suggest a simple read for rounding configuration, but the description says 'fetch the full details of a specific Field Productivity records by its identifier' which is inconsistent and misleading. This obscures the tool's true purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions or related tools. The statement 'Use this to fetch...' is vague and applies to the wrong resource, offering no actionable advice for the AI agent.

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