get_frame_summary

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

The description implies a read-only operation through the 'Get' verb and lists the return values, but it does not explicitly state behavioral traits such as absence of side effects, permission requirements, or limitations. Since no annotations are provided, the description partially covers transparency but lacks explicit statements.

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 concise and front-loaded with the core purpose, followed by a bulleted list of return fields. It avoids unnecessary words, though the bullet list could be slightly more compact.

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?

The description details the returned statistics but does not mention prerequisites (e.g., that a capture must be currently loaded) or state conditions. Given the tool's simplicity (no parameters), the description is mostly complete but could benefit from contextual guidance.

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?

The tool has no parameters, and the input schema coverage is 100% (vacuously). The description correctly omits parameter details, so the baseline score of 3 applies.

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 a summary of the current capture frame' and lists the statistics returned, clearly indicating the tool's purpose and what it provides. It distinguishes itself from sibling tools that focus on specific aspects (e.g., get_draw_call_details) by offering a high-level overview.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions for use. There is no explicit 'when to use' or 'when not to use' advice.

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