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. It hints at a guard/cache mechanism but does not explain what is checked, whether the operation is read-only, what happens on failure, or what a 'registered origin' requires. The behavioral context is too thin for a tool with no structured annotations.

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 short sentence and is front-loaded with the tool's resource, which is structurally efficient. However, its brevity comes at the cost of under-specification, leaving key terms undefined. It is concise but not sufficiently informative.

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 annotations, no output schema, and 0% parameter description coverage, the description should compensate by explaining behavior and the 'server' parameter. It only provides a vague guarded-list statement, leaving the agent without enough information to invoke the tool confidently. It is not misleading, but it is materially incomplete.

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 schema has one required parameter, 'server', with 0% description coverage, and the description never mentions it. The phrase 'registered origin' loosely suggests an origin/server concept but does not map to the parameter or explain acceptable values. An agent cannot determine what to pass for 'server' from the definition.

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 as 'tools/list' and qualifies it as 'guarded' through a 'cache guard' for a 'registered origin'. However, 'guarded' and 'cache guard' are unexplained jargon, so the actual effect of the tool is only vaguely conveyed. It does distinguish itself from siblings by being a list operation, but an agent may still not know exactly what it returns.

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 versus alternatives such as cache_exposure_verdict or guard_diff_check. It also does not state prerequisites, exclusions, or the meaning of a 'registered origin'. The agent must infer usage entirely from the name and vague context.

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