vizcom_status

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. Beyond that the description adds only the negative claim about browser/desktop control and says nothing about what a successful or failed check looks like, whether it makes a network call that can be slow or rate-limited, or what error surface to expect.

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 short sentences, front-loaded with the actual action, with no filler. The second sentence is somewhat cryptic in isolation but not padded.

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 and no parameters, the description is the only place return-value meaning could be conveyed, and it does not say what the auth check reports (boolean, account info, error text). For a simple diagnostic tool this is a modest but real gap; the safety profile is already handled by annotations.

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 tool takes zero parameters, so there is no parameter semantics for the description to carry; the baseline applies. Nothing in the description misleads about inputs.

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 gives a verb-plus-object ("Check API authentication"), so the core action is identifiable, but it never uses the tool name's framing of a general "status" check and does not say what status dimensions are reported. Against siblings that are all render/board operations the distinction is implicitly obvious, yet the description itself does not name or contrast any alternative.

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 when-to-use guidance: nothing says to call this first to validate credentials, or under what failure conditions an agent should reach for it. The only scoping statement is the negative "No browser or desktop control," which rules something out but does not steer selection among tools.

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