Update Company Segment Item

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that only supplied fields are changed and returns the modified object. However, it does not disclose authentication needs, rate limits, or idempotency behavior beyond what annotations provide.

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 concise, front-loaded with the purpose, and includes endpoint details. The Procore API line adds some context but is not strictly necessary. Overall, efficient.

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?

Given no output schema, the description mentions return of the modified object. Parameters are fully documented in schema. The description covers the essential behavior for an update 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?

All 7 parameters are described in the input schema (100% coverage). The description repeats required parameters and mentions partial updates ('only the supplied fields are changed'), but adds no meaning beyond what the schema already conveys.

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 'Update a specific Company Segment Item' and explains it updates Work Breakdown Structure records. It includes the endpoint and required parameters, distinguishing it from siblings like bulk_update_company_segment_items and create_company_segment_item.

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 says 'Use this to update an existing Work Breakdown Structure records' and lists required parameters, but does not provide when-not to use or explicitly mention alternatives. Sibling tools exist for bulk updates and creation, but no guidance is given on choosing between them.

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