toggle_pinned_stories

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds a note about indefinite availability, which provides some behavioral context (e.g., no time limit) but does not elaborate on side effects or reversibility. No contradiction with annotations.

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?

Single concise sentence with no filler. The key information (action, resource, audience) is front-loaded.

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 toggle tool with an output schema, the description covers the essential purpose and scope. It does not mention edge cases or prerequisites, but given the tool simplicity and the presence of an output schema, it is largely complete. The 'available indefinitely' caveat adds a minor, albeit ambiguous, note.

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 implies that the 'pinned' boolean controls pin/unpin, and 'story_ids' specifies which stories, but does not explicitly document the parameters or their formats. The parameter names are self-explanatory, but the description adds limited detail beyond the schema.

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 'Закрепить/открепить мои stories в профиле (доступно бессрочно)' clearly states a specific action (pin/unpin) on a specific resource (my stories in profile). It distinguishes from sibling tools like get_pinned_stories (read-only) and pin_message (for messages).

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 provides a clear context for when to use the tool: to pin or unpin the user's stories. It does not explicitly mention alternatives or exclusions, but the operation is self-evident and unambiguous among the story-related siblings.

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