Save Post

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

The annotations mark destructiveHint=true, but the description describes a simple save action (clicking Save), which is not destructive. This is a direct contradiction between the described behavior and the annotation, severely impairing transparency. The description also does not address any side effects or reversibility.

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 well-structured with a clear purpose statement, behavior explanation, and Args/Returns sections. It is concise but includes the unnecessary ctx mention, keeping it from a top score.

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?

Despite having an output schema and minimal complexity, the annotation contradiction is unresolved and the description lacks any usage guidance or discussion of side effects. This makes the description incomplete for an agent to safely and correctly invoke the tool.

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 provides useful meaning for post_url with an example and explains collection as optional, compensating for the 0% schema coverage. However, it lists 'ctx' as an argument that is not present in the input schema, which could mislead the agent about the actual accepted 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?

The description opens with 'Save a post to a collection,' which clearly states the verb and resource. It distinguishes this tool from siblings like like_post or follow_user by focusing on the Save action and optional collection specification.

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 by stating it navigates to a post and clicks Save, and optionally targets a collection. However, it offers no explicit when-to-use guidance versus alternatives, nor any exclusions or prerequisites.

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