st.doctor

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

With no annotations, the description carries the full behavioral burden. It does communicate that the tool is a check rather than a mutating operation, but it does not define what 'controllable' means or what response/error an agent should expect beyond the bare 'whether' wording.

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 front-loaded sentence with no filler, repetition, or extraneous detail. 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 zero-parameter health check the description is usable, but the absence of an output schema and annotations means it should also state the result shape and clarify what 'controllable' means (e.g., reachable, authenticated). It also leaves the relationship to sibling health/verify tools unaddressed.

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?

The input schema has zero properties, so there are no parameters for the description to document. The zero-parameter baseline of 4 applies, and the description's focus on the target runtime is consistent.

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 the specific verb 'Check' against the resource 'target SillyTavern runtime' and clearly states the tool tests controllability, so it is not a tautology. However, it does not explicitly distinguish itself from similar diagnostic/control siblings such as st.verify or st.runtime.control.

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?

No guidance is provided about when to run this check versus alternatives like st.verify or st.runtime.control. The pre-flight use case is only implied by the word 'controllable,' leaving an agent without explicit decision criteria.

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