find_draws_by_shader

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

No annotations are provided, so the description carries full burden. It explains the matching behavior (partial match), the search domain (shader names or entry points), and the return structure (list with event IDs and match reasons). It does not mention performance or limitations, but the query nature is clear.

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 short paragraph followed by a bullet-like list for args. It is front-loaded with the main purpose in the first sentence, and every line provides necessary information without redundancy.

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 an output schema exists (context signals), the description need not detail return fields, but it still summarizes 'list of matching draw calls with event IDs and match reasons.' Parameters are fully explained, and the tool's purpose is clear in the context of sibling tools.

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 explain the parameters. It does so clearly: shader_name is 'Partial name to search for in shader names or entry points', and stage is 'Optional shader stage to search (if not specified, searches all stages)'. This adds meaning beyond the schema types.

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 begins with 'Find all draw calls using a shader with the given name (partial match).' This specifies the verb 'find' and the resource 'draw calls using a shader', and the partial match detail differentiates it from sibling tools like find_draws_by_resource or find_draws_by_texture.

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 purpose is clear from the name and description, implying when to use this tool over siblings. However, it lacks explicit when-not or alternative suggestions, such as stating to use other find_draws tools for resource-based searches.

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