pin_tweet

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

With no annotations provided, the description discloses the destructive nature (replacing existing pin) and the behavior of automatic unpinning. It could mention rate limits or error handling, but it adequately covers the key behavioral traits.

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 with a clear warning emoji and front-loaded essential information. Every sentence adds value without redundancy.

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 the absence of annotations and an output schema, the description fully covers the tool's purpose, key behavioral warning, and parameter meaning. It is complete for a simple action with one parameter.

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 describes the tweet_id parameter completely. The description adds no extra meaning beyond the schema's explanation, so it meets the baseline for high schema coverage.

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 explicitly states 'Pin a tweet to your profile' with the verb (pin) and resource (tweet), and clarifies it replaces any existing pinned tweet, distinguishing it from sibling tools like unpin_tweet.

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?

It explains the constraint that only one tweet can be pinned and that a previous pin is automatically unpinned. This provides clear context for when to use it, though it doesn't explicitly state when not to or suggest alternatives.

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