Create Equipment Category

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

Discloses that it creates a record and returns the object on success (HTTP 201), which aligns with annotations (readOnlyHint=false). Adequately adds endpoint details but does not go beyond what annotations imply.

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?

Short but contains redundancy (e.g., 'Create a new...' repeated, 'Field Productivity records' mentioned twice). Could be more concise without losing clarity.

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?

Covers endpoint, HTTP response, required params, and module. Lacks details on the returned object structure (no output schema) and error conditions, leaving some gaps for a creation tool.

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 covers all parameters with descriptions; description merely restates required parameters. No additional semantic value beyond the schema, resulting in a baseline score of 3.

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?

States it creates an equipment category entry for Field Productivity in Procore, specifies required parameters and endpoint. However, lacks differentiation from sibling tools like create_equipment_category_company or create_equipment_category_project, which may cause confusion.

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?

No guidance on when to use this tool versus alternatives (e.g., company vs project scope). Does not specify prerequisites or exclusions, leaving the agent to infer context from the endpoint.

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