set_page_mode

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

Annotations already indicate the tool is idempotent, non-destructive, and not read-only. The description adds valuable context about scope ('applies to every member') and clarifies that it affects all members, which is beyond annotation coverage. No contradictions 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?

The description is two sentences with no fluff. The core purpose is front-loaded, and the differentiation from set_user_settings is placed at the end for clarity. Every word 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 setter with two parameters and no output schema, the description is sufficient. It explains what the tool does, its scope, and distinguishes from related tools. It doesn't mention prerequisites or error cases, but these are not critical for this simple operation.

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 50%: only 'mode' has a description, while 'collectiveId' lacks one. The description adds minimal parameter-specific meaning—it repeats the view/edit enum but does not clarify the collectiveId semantics or any parameter formatting. It fails to compensate for the missing schema description.

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 clearly states the action ('Set the default page mode'), the resource ('a Collective'), and the specific behavior ('whether pages open in view or edit mode'). It also distinguishes from a sibling tool (set_user_settings) by noting the scope difference, making the purpose 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?

The description explicitly contrasts with set_user_settings, indicating when to use this tool (collective-wide) versus the alternative (per-user). This gives clear usage guidance and differentiation among siblings.

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