find_draws_by_resource

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

With no annotations, the description carries full burden. It fully discloses the search scope (shaders, SRVs, UAVs, render targets, depth targets) and the return structure (list of matching draw calls with event IDs and match reasons). No hidden behaviors or contradictions.

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 structured with a clear opening line followed by an Args section. It is not overly long, but the Args section repeats the parameter name unnecessarily. Slightly redundant but still effective.

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 single-parameter search tool with an output schema, the description covers purpose, parameter format, search scope, and return information. No additional details are needed for completeness.

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 coverage is 0%, so the description must compensate. It provides an example format (e.g., 'ResourceId::12345' or '12345'), adding meaning beyond the blank schema. However, it could include more detail on allowed patterns or constraints.

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?

Starts with a clear verb+resource: 'Find all draw calls using a specific resource ID (exact match)'. Immediately distinguishes from sibling tools like find_draws_by_shader and find_draws_by_texture by specifying the search key.

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?

Provides context by stating exact match and listing search targets (shaders, SRVs, etc.), but does not explicitly state when to use this tool versus alternatives or when not to use it. The differentiation from siblings is implied by the parameter.

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