get_starred_entries

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

No annotations are provided, so the description must carry the full burden. It reveals pagination with page and per_page, and a maximum per_page of 100. However, it does not state whether the operation is idempotent, requires authentication, or if there are rate limits. The 'get' verb implies read-only, but explicit safety info is missing.

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 extremely concise: two sentences for purpose and a brief list for parameters. Every sentence earns its place; no fluff or repetition.

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 is a simple paginated list with an output schema (presumably describing return fields), the description is fairly complete. It could mention output format or ordering, but those are likely covered by the output schema. Missing info about whether entries include full content is minor.

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 input schema has 0% description coverage (no descriptions for parameters), so the description compensates by explaining page number, per_page count, defaults, and maximum. This adds significant meaning beyond the schema, which only provides types and defaults.

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?

Description clearly states it retrieves starred (bookmarked) article entries from Feedbin, which is a specific resource. It distinguishes itself from siblings like get_entries (all entries) and get_read_entries by the 'starred' qualifier.

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 implies usage for retrieving saved/bookmarked entries but does not explicitly state when to use this tool versus alternatives like get_starred_entry_ids (which returns only IDs) or star_entries (which modifies state). No when-not or comparative guidance.

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