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

With no annotations provided, the description fully discloses the behavioral impact: enabling shares exposes a public preview without sign-in, disabling makes the link stop working, and it does not affect the underlying confession's read permissions. This is strong behavioral context for a mutation-like operation.

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?

Three sentences, no filler, with the core action front-loaded and the clarifying limitation at the end. Every sentence earns its place.

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 boolean/int tool with no output schema, the description covers the action, scope, ownership constraint, and side effects. An agent has enough to select and invoke this tool correctly.

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 coverage is 0%, so the description must carry the parameter meaning. It clearly explains 'allow_shares' (on/off behavior) and ties 'confession_id' to 'one of your own confessions', though it stops short of explicitly stating 'confession_id is the numeric ID of the confession to modify.' It compensates well but not perfectly.

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 names the exact action ('Turn the share link on or off'), the resource ('one of your own confessions'), and clearly distinguishes itself from visibility/publishing controls. It leaves no ambiguity about what the tool is for.

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 explains both when to use it (to control the share link) and when not to use it (to change who can read the confession itself), pointing to the publish-time visibility setting instead. This gives an agent an explicit decision rule among related operations.

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