update_requested_item

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

Discloses partial update behavior and record identification via sys_id; no annotations so description carries full burden, which it meets adequately.

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?

Single, information-dense sentence with no redundancy; parenthetical filter hint is efficiently placed.

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 core functionality and record type, but lacks return value, error handling, or missing prerequisites; adequate for a straightforward 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?

Schema has 0% coverage; description clarifies that 'fields' is a JSON object for updates and mentions partial update, but doesn't detail allowed keys or structure.

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 specifies verb 'Update', resource 'requested item (sc_req_item)', and distinguishes from siblings by mentioning it's a line item under a parent Request.

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?

Provides context for when to use this tool (for sc_req_item records) and includes a filtering hint, but does not explicitly exclude alternatives.

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