get_extension_status

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

No annotations are provided, so the description carries the full behavioral burden. It says it checks connectivity and returns 'current status' but does not disclose what status fields are reported, what happens (or what error surfaces) when the extension is disconnected, or whether it is a safe, side-effect-free read. For a diagnostic tool this is thin.

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?

A single front-loaded sentence that states the connectivity check first and the status retrieval second, with no filler. Appropriately sized for a simple zero-argument tool.

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?

The tool is simple (0 params) but has no output schema, so the description is the only place a caller could learn what 'current status' returns. It does not describe the return shape or the disconnected-state behavior, leaving a modest gap for an agent trying to interpret the result.

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 per the baseline there is nothing for the description to disambiguate. No parameter semantics are required and none are missing.

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 a specific verb+resource: check whether the BNBOT Chrome extension is connected and retrieve its status. This is clearly distinct from the action-oriented siblings (scrape_*, navigate_*, post_*), which are all about operating on content rather than reporting extension health. No sibling is named, so it stops short of explicit differentiation, but the purpose is unambiguous.

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 call this tool versus alternatives, no mention of it as a prerequisite/health check before other operations, and no exclusions. Usage is only implied by the name. Nothing tells the agent why or when it should reach for this over the rest of the toolset.

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