get_exhibition_mode

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

Discloses that it 're-delivers the same standing restriction instruction as enter_exhibition_mode for whichever state is current', which adds behavioral context beyond the empty input schema. No annotations present, so description carries the burden.

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?

Two sentences with no redundancy. Front-loaded with the core purpose, followed by usage guidance. 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 boolean report tool, the description is mostly complete. It does not specify the output format, but given the tool's simplicity, this is a minor gap. No output schema exists to compensate.

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?

No parameters, so input schema coverage is 100%. Description redundantly states 'No arguments.' but adds meaningful context about the tool's purpose, which is sufficient for a zero-parameter tool.

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 states 'Report whether exhibition mode is currently on.' It clearly identifies the verb (report) and resource (exhibition mode status), and distinguishes from sibling tools like enter_exhibition_mode and exit_exhibition_mode.

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?

Specifies when to call: 'if you're unsure whether it's still active (e.g. at the start of a new turn after a long gap)'. Provides context for usage but does not explicitly state when not to use or list alternatives.

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