sherweb_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is minimal and doesn't explain what 'credentials status' reports (valid/invalid, expiry), whether it makes network calls, whether it requires prior authentication setup, or what a failure looks like. For a status-checking tool with zero annotation coverage, this is underspecified.

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 efficient sentence with no wasted words. It's appropriately concise for a tool with zero parameters. However, it could have used the brevity freedom to add behavioral context without bloating.

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?

Despite having zero parameters and a simple purpose, the tool operates within a 10-tool Sherweb ecosystem. The description doesn't explain what the output looks like (no output schema), what 'credentials status' means in practice, how 'available domains' relates to other tools, or when a user would want this information. For a status tool that likely serves as a pre-flight check for the rest of the API tools, more context would materially help an agent.

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 has 0 parameters and 100% schema description coverage (an empty schema is trivially fully covered). With no parameters, the description has no parameter semantics responsibility. The description accurately reflects that it takes no inputs, so a baseline 4 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 'Show credentials status and available domains' states a clear action ('show') with a specific resource (credentials status and available domains). However, it doesn't distinguish itself from the sibling tools like sherweb_navigate or the various list/get tools, and 'credentials status' is somewhat vague about whether these are API credentials, user credentials, or something else.

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 given on when to use this tool versus its siblings. There's no mention of whether it should be called first to verify credentials, to discover available domains before other operations, or any other contextual usage direction. With 10 sibling tools, this lack of usage guidance is a notable gap.

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