get_latest_feed

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

The description implies a read-only operation through 'Get', but does not explicitly state it is non-destructive or mention any permissions or side effects. Annotations are absent, so more explicit transparency would be beneficial.

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 very concise with one sentence and a structured parameter list. No unnecessary words, but it could include a bit more context without being verbose.

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 no output schema, the description does not explain the return format or error cases. It covers the basic purpose and parameter but lacks completeness for a tool that returns data.

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 explains the 'count' parameter as 'Number of bookmarks to fetch' and notes the default value, adding value beyond the schema which only defines type and default. Since there is only one parameter, this coverage is good.

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 'Get latest bookmarks from Raindrop.io feed.' The verb 'Get' and resource 'latest bookmarks' are specific, and it is distinct from siblings like add_bookmark or search_bookmarks.

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 on when to use this tool vs alternatives. It does not mention when not to use it, or provide context for choosing between siblings.

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