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

Annotations already cover readOnly (false), destructive (false), and idempotent (true). The description adds the detail about the default behavior (star=true) and the idempotency key's role, but doesn't add much beyond annotations. Since annotations cover the safety profile, 3 is baseline.

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?

Two sentences with no wasted words. It front-loads the action and the toggle condition, then immediately defines the key parameter. Perfectly concise for the tool's complexity.

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 the tool's simplicity and the rich annotations (idempotentHint, openWorldHint, output schema present), the description is sufficient. It covers the essential usage details, though it could mention that the action is reversible (star toggling), but that's implied.

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 100%, so the schema documents all parameters. The description reinforces the meaning of conversation_linkedin_id and the star toggle, but the schema already does this. It adds slight value by specifying that star=false removes the star, which matches schema default.

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 the verb 'star or unstar' and the resource 'LinkedIn conversation', exactly matching the tool name. It also distinguishes the two actions and references the specific ID needed, making the purpose unambiguous.

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 provides clear context on how to use the tool: set star=false to remove the star, and identifies the conversation ID source. It doesn't explicitly compare to siblings like archive_conversation or delete_conversation, but the purpose is distinct enough that an agent would know when to use it.

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