Pin or unpin a Saved sub-dialog

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

The description states the core behavior of pinning/unpinning, which aligns with the openWorldHint annotation. However, it discloses no additional behavioral context such as idempotency, error conditions, or how the operation affects the sub-dialog. The annotation is generic, so the description adds minimal extra value.

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, front-loaded sentence with no filler. It immediately conveys the action and target without unnecessary repetition.

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?

The description provides adequate context for a simple toggle action, but it doesn't clarify prerequisites (e.g., the sub-dialog must be forum-style) or how success/failure is communicated. Given the absence of an output schema, some elaboration on expected behavior would improve completeness.

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 does not explain any parameters. The schema covers peer and pinned, but accountId is left undocumented. With 67% schema coverage, the description should help fill the gap for accountId but doesn't, leaving a clear deficiency.

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, 'Pin/unpin one of the forum-style sub-dialogs inside Saved Messages,' clearly states the action and target, using a specific verb and resource. This distinguishes it from sibling tools like pin_message, which operate on regular 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 implies the tool is for managing sub-dialogs in Saved Messages but does not explicitly state when to use it over alternatives or when not to use it. For instance, it doesn't mention that pin_message is for regular messages, leaving usage to be inferred from context.

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