stars_list

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

No annotations exist, so the description must disclose behavioral traits. It fails to mention pagination despite the schema having pagination parameters (count, cursor, limit, page), and does not explain what 'detailed=True' changes beyond 'full response'. This omission leaves the agent unaware of important 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 exceptionally concise: two short sentences that front-load the purpose. Every word adds value, with no redundant or vague phrasing.

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?

Despite having an output schema, the description does not cover critical details like pagination behavior, the effect of team_id, or the meaning of 'detailed'. Given the parameter count and lack of schema documentation, the description is insufficient for confident tool usage.

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?

With 0% schema description coverage, the description must compensate for all 6 parameters. It only briefly addresses 'detailed', giving minimal meaning. The other five parameters (count, cursor, limit, page, team_id) receive no explanation, making it impossible for the agent to use them correctly without external knowledge.

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 action ('List') and resource ('starred items for the calling user'), making the tool's purpose immediately obvious. It distinguishes itself from sibling tools like stars_add and stars_remove by focusing on listing rather than modifying starred items.

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?

While the description implies the tool is for viewing starred items, it does not explicitly state when to use it versus alternatives like saved_list or stars_add. There is no 'when not to use' guidance, leaving the agent to infer usage from context.

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