scan_idle_resources

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

The description states the tool is read-only and does not modify resources, which is critical for a scanning tool. However, with no annotations provided, it does not disclose other behavioral aspects such as output format or execution duration.

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 very concise with two sentences, front-loading the purpose. It contains no filler, but could potentially include more detail without significant bloat.

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?

Given the lack of output schema and many sibling tools, the description fails to explain what the tool returns or how to interpret results. It is incomplete for a scanning 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 already describes the 'region' parameter with 100% coverage, and the description adds no further semantic value. Baseline score of 3 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 clearly states it runs an 'Idle Resources security scanner', specifying the resource type and action. Among sibling tools like scan_access_analyzer_findings and scan_ssl_certificate, this description uniquely identifies its focus on idle resources.

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 mentions 'only' and 'Read-only' but provides no guidance on when to use this tool versus alternatives like scan_all or other specific scanners. It lacks context for optimal usage.

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