get_starred_entry_ids

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

No annotations provided. Description states it's a read operation returning a flat array, but doesn't disclose any permissions, rate limits, or side effects. Adequate for a simple tool but could be more thorough.

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, no redundant information, front-loaded with purpose, efficient and clear.

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?

Simple tool with output schema present; description covers purpose, output type, and efficiency context. Could mention that it returns all starred IDs (implied) but sufficient.

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?

No parameters, so baseline is 4. Description adds value by explaining the output format and efficiency, though not directly about parameters.

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?

Clearly states 'Get the list of all starred entry IDs' and specifies output type ('flat array of integer entry IDs'). Differentiates from sibling get_starred_entries by noting efficiency for just IDs/counts.

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?

Explicitly says when to use this tool ('more efficient than fetching full entries when you just need counts or IDs'), but doesn't mention when not to use or alternatives for other purposes.

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