Create Gps Position

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

Description adds that it returns HTTP 201 on success and lists required parameters, but goes beyond annotations minimally. Does not discuss authorization, rate limits, or potential side effects beyond creation. Annotations already indicate it's a write operation (readOnlyHint=false). No contradiction.

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?

Description is brief and front-loaded with the core purpose. Some slight redundancy ('Create a new Gps Position' and 'Use this to create... Creates...') but overall efficient and well-structured.

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 creation tool with a comprehensive input schema (100% coverage), the description provides essential context: purpose, required parameters, endpoint, and success return. It does not require extensive additional detail given the schema richness.

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 baseline is 3. Description lists required parameters but provides no additional semantics beyond what the schema already describes. Does not explain purpose of altitude or accuracy fields, though schema covers them adequately.

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?

Clearly states the action 'Create a new Gps Position' and the resource, distinguishing it from sibling list/show tools. Mentions it creates Field Productivity records in Procore, providing specific context.

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?

States 'Use this to create a new Field Productivity records', giving a clear use case, but does not provide explicit guidance on when not to use or alternatives among sibling tools. Lacks exclusions or prerequisites beyond listing required parameters.

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