update_item

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

With no annotations, the description carries the full burden of explaining behavioral implications, but it only states that the tool updates. It does not disclose whether the update is partial or full, what side effects occur, what permissions are required, or whether it is reversible. The agent is left without any behavioral context.

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 extremely short but under-specified. It is not meaningful conciseness; it is a restatement of the tool name that fails to use its sentence to convey any actionable guidance.

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 annotations, no output schema, and a required free-form body parameter, this description is far from complete. An agent cannot determine how to construct the request body, what the update affects, or what the expected result is.

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 coverage is only 50%: id has no description, and body is an open object described only as 'Request body passed through to Bigcapital'. The tool description provides no additional meaning about either parameter, leaving the required request body structure completely unspecified.

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 'Update an item.' simply restates the tool name in natural language and adds no new information. It names the resource but does not distinguish update_item from the many other update_* siblings beyond the resource label already present in the tool name.

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?

There is no guidance about when to use this tool versus alternatives such as create_item, get_item, or list_items. No context, prerequisites, or exclusion conditions are provided, so an agent must infer usage entirely from the tool name.

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