web_protect_list

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

There are no annotations, so the description carries the behavioral burden. The word 'list' implies a read-only enumeration, but the description does not explicitly state that it has no side effects, what scope it covers, or whether special authentication is required. This is minimal but not misleading.

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 concise, with no filler words, and places the resource type up front. It is slightly terse and uses a noun phrase rather than a clear imperative, but for a no-parameter list tool this is appropriately sized.

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 parameters and an output schema present, the description does not necessarily need to explain return values. However, it lacks usage context and explicit behavioral detail such as scope or read-only guarantees, making it only minimally complete for an agent deciding whether to call this tool.

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 no parameter documentation is needed. The description adds no param-level detail, but that is acceptable because there are no parameters to explain.

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 identifies the resource (directory password-protection) and implies a list/read operation, which is clearly tied to the tool name. It distinguishes the tool from most siblings because no other sibling covers this resource, though it does not explicitly state an imperative verb.

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?

The description gives no guidance on when to use this tool or when to prefer an alternative. There is no mention of scope, prerequisites, or relationship to other tools, so the agent must infer usage entirely from the name.

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