binlog_status

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

The readOnlyHint annotation already establishes the safety profile, and the '[READ]' prefix merely restates it. The description does add value by enumerating the data surfaced (GTID mode, downstream replicas), but it says nothing about privileges required, whether it is safe to poll, or freshness of the replica data.

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 tight lines with the core capability front-loaded. The '[READ]' prefix is mildly redundant with the readOnlyHint annotation, but it costs little.

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?

With no output schema, the description carries the burden of explaining what comes back, and it only gestures at the categories (config, GTID, replicas) without indicating the shape of the response. Adequate to identify the tool, thin for interpreting its output.

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% and the single 'target' property has no description in the schema. The description compensates by explaining that it is a 'Target name from config' and that omitting it selects the default, which is exactly the semantics an agent needs.

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 specific resource and dimensions reported: binary-log configuration, GTID mode, and connected downstream replicas. That is far more informative than a bare 'status' label, though it never explicitly distinguishes itself from the nearby replica_status tool.

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 on when to reach for this over replica_status, show_status, or show_variables, nor any stated prerequisites. The only usage hint is the parameter note 'omit for the default', which covers invocation but not tool selection.

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