get_raindrop

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

No annotations are provided, so the description carries full burden. It states it 'fetches' a raindrop, implying a read-only operation, but does not disclose behavioral traits such as authentication requirements, error handling (e.g., invalid ID), rate limits, or response format. The description is minimal and misses key operational details.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by a brief 'Args' section. Every sentence earns its place with no redundant information, making it efficient and easy to parse.

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's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks information on return values, error cases, and behavioral context (e.g., what happens if the ID doesn't exist). For a tool with zero annotation coverage, more detail is needed to ensure reliable agent use.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining 'raindrop_id' as 'ID of the raindrop to fetch', which clarifies the parameter's purpose beyond the schema's basic type. However, it does not provide format details (e.g., integer range) or examples, leaving gaps in documentation.

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 specific action ('Get a single raindrop') and resource ('from Raindrop.io by ID'), distinguishing it from sibling tools like 'get_raindrops' (plural) and 'get_collection_by_id' (different resource type). The verb 'fetch' precisely indicates retrieval without ambiguity.

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 context by specifying 'by ID' and listing the required parameter, but does not explicitly state when to use this tool versus alternatives like 'get_raindrops' or what prerequisites exist (e.g., needing a valid ID). It provides clear intent but lacks explicit comparison or exclusion guidance.

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