find_draws_by_texture

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

The description discloses that it searches across SRVs, UAVs, and render targets, which adds behavioral context beyond the tool's name. It also mentions the return format (list with event IDs and match reasons). No annotations were provided, so the description handles this well.

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 extremely concise with three short sentences. The main purpose is front-loaded, followed by parameter details and return value description. Every sentence adds value.

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 that an output schema exists (though not shown), the description appropriately summarizes the return format. It covers the search scope and return details sufficiently for a tool with one parameter.

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?

With 0% schema description coverage, the description compensates by explaining the parameter 'texture_name' as 'Partial name to search for in texture resource names', adding meaningful interpretation beyond the schema's type definition.

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 verb 'Find', the resource 'draw calls', and the scope 'using a texture with the given name (partial match)'. It effectively distinguishes itself from sibling tools like find_draws_by_resource and find_draws_by_shader.

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 specifies that the search is a partial match on the texture name, which guides usage. However, it does not explicitly mention when to use this tool versus siblings, but the purpose is clear enough.

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