baasix_realtime_disable

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention whether disabling realtime is reversible, whether existing realtime subscribers are affected, whether configuration is removed or paused, or what the response/outcome looks like. This is a notable gap for a state-changing tool.

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 clear sentence with no filler, and the action is front-loaded. It is appropriately concise for a one-parameter operation, though it could have been stronger by including missing usage and side-effect context.

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 low-complexity tool with one fully documented required parameter, the description and schema are syntactically sufficient for an agent to invoke the tool correctly. However, the absence of annotations and output schema leaves operational context and impact behavior unstated, so completeness is adequate but not strong.

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 description coverage is 100%, and the collection parameter is already described as 'Collection name to disable realtime for.' The description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 uses a specific verb ('Disable') and a clear target ('realtime for a collection'), which immediately identifies the operation. It also distinguishes itself from sibling tools such as baasix_realtime_enable and baasix_realtime_status by making the opposite action explicit.

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?

There is no guidance about when to use this tool versus baasix_realtime_enable or other realtime-related tools, and no prerequisites or conditions are mentioned. The only usage signal comes from the sibling tool names, so the description itself offers no when/when-not advice.

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