get_draw_call_details

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

No annotations are provided, so the description carries the full burden. It adds that response includes 'vertex/index counts, resource outputs, and other metadata', but does not disclose if it's read-only, permissions needed, or side effects, which are minimal for a get tool.

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?

Two sentences plus an elegantly placed Arg section. Front-loaded purpose, no redundant wording, efficient structure.

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?

Single parameter, no annotations, but has output schema (unseen). Description mentions included data types, which is sufficient for a simple retrieval tool. Could hint at output format, but not essential.

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 has `event_id` with 0% description coverage. The description adds 'The event ID of the draw call to inspect', clarifying the parameter's role and compensating for the schema's lack of detail.

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 'Get detailed information about a specific draw call', which is a specific verb+resource combination. It distinguishes from sibling `get_draw_calls` (plural) that likely lists calls, and other find-style tools.

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 implies usage when one has an `event_id` for a specific draw call, and context from siblings suggests it's for drill-down after listing. No explicit when-not or alternatives, but clear enough.

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