get_raindrop

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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'Get a single bookmark by ID,' which implies a read operation, but it does not disclose what happens for missing IDs, what the response contains, or whether any side effects occur. The verb 'Get' suggests safety, but it is not explicitly stated.

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 one short, front-loaded sentence that states the action and the key selector with no filler or redundant phrasing. Every word contributes to understanding the tool's core purpose.

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?

For a simple one-parameter lookup, this is minimally sufficient: the agent knows the action, the resource, and the identifier to supply. However, with no output schema and no annotations, the description does not cover expected return behavior, failure handling, or how this tool relates to the sibling get_raindrops, so fuller context would improve usability.

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 schema already documents the single parameter as 'Bookmark ID' with 100% coverage. The description's 'by ID' simply restates the parameter's meaning and adds no additional format, validation, or usage nuance, so it does not exceed the schema baseline.

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 uses a specific verb and resource: 'Get a single bookmark by ID.' The word 'single' and the ID selector clearly distinguish this from get_raindrops and other collection-level tools, so an agent can identify the tool without opening any schema.

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 the use case: fetch exactly one bookmark by its identifier. However, it does not explicitly state when to choose this over get_raindrops, nor does it mention any exclusions or alternative routing. The guidance is present only by implication.

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