Discover Resources

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Find resources across services by tags' and doesn't disclose whether this is a read-only operation, whether it queries AWS APIs directly, whether it can be slow, whether it requires prior profile/account selection, or what happens with no matching resources. The output schema exists but the description doesn't explain the behavior beyond the basic search.

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 with no wasted words. It is front-loaded with the verb and resource. However, it is so brief that it sacrifices useful detail, which is a conciseness tradeoff that doesn't fully serve the agent.

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 tool has 3 parameters, no annotations, and a 0% schema description coverage, the description is incomplete. The output schema exists, but the agent still lacks guidance on how to construct the tags object, whether region/services are filters or required for certain services, and what the returned resources look like. A more complete description would explain the search scope and result behavior.

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?

Schema description coverage is 0%, so the description must compensate for the schema's lack of parameter documentation. The description only mentions 'tags' implicitly and says nothing about 'region' or 'services' parameters. The schema shows types and defaults, but the description adds no meaning about how these parameters interact or what values are expected.

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 states a clear verb ('Find') and resource ('resources across services by tags'), which distinguishes it from many sibling tools. However, it doesn't specify what kind of resources or what 'across services' means concretely, and it doesn't differentiate it from similar discovery tools like find_idle_resources or map_dependencies.

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?

No guidance is given about when to use this tool versus alternatives. The description implies tag-based discovery, but it doesn't state when an agent should prefer this over find_idle_resources, map_dependencies, or aws_query. There are no exclusions or context cues.

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