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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the visible outcome (item appears in the sidebar) but omits the significant behavior implied by the schema: every star operation requires a full item payload plus expected_version, i.e., optimistic concurrency, and nothing is said about what happens on a version mismatch.

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?

A single front-loaded sentence with no filler, and the effect clause is placed after the action. Brevity is not the problem here; the sentence simply stops before the details the schema makes necessary.

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 mutation tool with a nested object parameter, a required version field, no output schema and zero schema description coverage, the description is far too thin. An agent cannot infer from it that it must supply a complete item record or a current version, which are the two most likely sources of failure.

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 0% across three required parameters, including a nested item object with id/name/route, so the description must compensate and does not. 'Stars or unstars' vaguely maps to the boolean 'starred', but expected_version and the entire nested item structure are left completely unexplained.

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 a specific verb pair (stars or unstars) plus the resources affected and the observable effect ('shows in the sidebar'). An agent can tell this is the write counterpart to list_starred, though the description never names that sibling or clarifies that the generic 'item' object covers requests, collections and projects.

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?

Usage is only implied: the toggle semantics of 'starred' and the sidebar effect hint at when to call it, but there is no explicit when-to-use, no mention of list_starred as the read path, and no stated prerequisites for obtaining the current version.

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