handle_get_app_sheets

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

No annotations are provided, so the description bears full responsibility. It describes the steps (connects, opens app, creates SheetList, retrieves metadata) but does not disclose potential side effects, authentication requirements, or rate limits. Adequate but not exhaustive.

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 few sentences long, front-loaded with the purpose. It could be slightly more concise (e.g., 'Retrieve all sheets from a Qlik Sense app' instead of the longer first sentence). No waste, but some 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 the presence of an output schema (not shown but indicated), the description need not explain return values. It covers the process adequately. However, it lacks usage guidelines or caveats, making it slightly incomplete.

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 100%, so baseline is 3. The tool description adds minimal value beyond the schema's param descriptions, e.g., it repeats 'retrieves all sheet metadata'. No additional clarification on format or usage.

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 tool retrieves Qlik Sense sheets, with specific verb+resource. The sibling tools (e.g., handle_get_app_dimensions, handle_get_app_fields) indicate distinct resources, making this one unambiguous.

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 explains the tool connects to a server and retrieves sheets, but does not explicitly tell when to use this tool versus alternatives like handle_get_sheet_objects. However, the context of sibling tools and the name imply it is for listing all sheets.

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