security_pools

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

The readOnlyHint=true annotation already establishes this is a safe read. The description adds a small amount of context with 'per-pool history kept while the view refreshes,' hinting at refresh/staleness behavior, but it is cryptic and does not clarify what is cached or how fresh the data is.

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?

It is a single short sentence, so it is not bloated, but it is not front-loaded with a verb or a clear subject and the parenthetical is hard to parse. The brevity comes at the cost of clarity rather than from disciplined editing.

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, the description carries the burden of explaining what data comes back, and it does not: 'tab data' does not tell an agent what fields, pool attributes, or history entries to expect. For a read-only data-fetch tool, this leaves the agent guessing about the return shape.

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 nothing for the description to document and the baseline is 4. The description appropriately does not invent parameters.

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 says 'Resource pools tab data,' which names the resource but supplies no verb and no clear statement of what the tool actually returns or does. It reads like a UI tab label rather than a tool purpose, and it does not distinguish itself from siblings such as resource_pool_status or security.

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, no prerequisites, and no mention of alternatives like resource_pool_status. The parenthetical about history is a data-behavior note, not usage guidance.

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