star

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Star a message' with no information on side effects (e.g., whether it toggles a star), required permissions, or reversibility (though sibling 'unstar' exists). The lack of detail leaves the agent uncertain about the tool's behavior.

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 a single sentence, which is overly terse. While conciseness is valued, it sacrifices necessary detail. Every word earns its place, but the description fails to include essential context about parameters or usage, making it incomplete rather than efficiently succinct.

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 three parameters (including optional auth credentials) and no output schema, the description is completely inadequate. It provides no information about return values, error handling, or how to use the optional fields. The tool's complexity requires more context for successful agent operation.

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?

The description adds no meaning to the three parameters. Schema descriptions are missing (0% coverage), and the description does not explain the roles of 'account' and 'password', nor that 'message_id' is required. The agent has insufficient information to correctly invoke the tool.

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 'Star a message' clearly states the action and object, but it does not distinguish this tool from siblings like 'unstar' or 'mark_important'. It provides only the basic verb+resource, lacking any context about what starring entails (e.g., marking a message as important or bookmarked).

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing an authenticated account, or when starring is appropriate compared to other actions like labeling or marking as important.

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