set-journal-page-visibility

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

Discloses that it sets page ownership default and does not modify content, which is key behavioral trait. With no annotations, description carries full burden; it is adequate but does not cover permissions or side effects.

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?

Concise two sentences that front-load the key action. Could be slightly tighter, but no unnecessary words.

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?

Adequate for a simple toggle tool with no output schema. Explains the core behavior and usage scenario. Lacks details on error cases or return value, but that's acceptable given complexity.

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 already describes all parameters (100% coverage), but description adds context: 'flip' implies toggling, and explains playerVisible as 'a handout players can OBSERVE' and GM-only. Enhances understanding beyond raw 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?

Clearly states it flips a journal page between player-visible and GM-only, specifying the verb 'flip' and resource 'journal PAGE'. Distinguishes from updating the whole journal by explicitly noting it does not rewrite content.

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?

Provides explicit guidance on when to use: to reveal/hide an existing page instead of rebuilding the whole journal. Includes a concrete example (page from an append). Lacks explicit when-not-to-use, but context is clear.

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