Find Untagged Resources

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

Description adds that results include specific fields, returns empty list if all tagged, and explains the business impact. Annotations already indicate it's safe and idempotent, but the description provides useful behavioral context beyond them.

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?

Four sentences, no wasted words. First sentence states purpose, second details output, third explains importance, fourth gives usage guidance. Efficient and well-structured.

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?

For a simple tool with one parameter and no output schema, the description covers the output format, edge case (empty list), and business relevance. Complete and sufficient.

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 single parameter 'provider' is fully documented in the schema with enum values. The description adds meaning by explaining the output structure and the empty list case, going beyond what the schema provides.

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 the tool finds resources without tags/labels, specifying the returned fields (name, type, resource group/project, location). It distinguishes from siblings like 'get_cost_by_tag' which deals with tagged 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?

Explicitly says to use when the user asks about tagging compliance, governance, or cost attribution gaps. Does not mention when not to use or alternatives, but the context is clear given the sibling list.

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