Pin one of your own statuses to the top of your profile

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which cover the basic safety profile. The description adds no behavioral context beyond that, such as whether pinning replaces a previously pinned status or whether it requires an unpin first. No contradiction exists, but no extra value is added.

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 a single sentence with no redundancy, but it simply restates the title and lacks substantive information. It is concise but not information-dense; it earns its place only barely.

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 two-parameter tool with no output schema and helpful annotations, the description is minimally sufficient. However, it does not explain the effect of pinning on an existing pin, any rate limits, or what the response contains, leaving minor but relevant gaps for a complete usage picture.

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 100%, with both parameters clearly described: 'id' as the status id and 'account' explaining matching rules and default behavior. The description itself does not mention parameters, but the schema adequately documents them, so the baseline of 3 applies.

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 states a clear verb ('Pin') and resource ('your own statuses') with the location ('top of your profile'). It is distinguishable from the sibling 'unpin_status' by action direction, but the description does not explicitly contrast with other pin-related tools. Still, the core purpose is unambiguous.

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 is given on when to use this tool versus alternatives, nor any prerequisites such as needing an existing status or the effect of re-pinning. The description implies the user has a status to pin but offers no decision support or exclusions.

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