superset_report_get

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

With no annotations provided, the description carries the full burden for behavioral disclosure. The verb 'Get' implies a read-only operation, and the description notes the prerequisite of calling the list tool first, but it does not explicitly confirm read-only safety, permissions, or error behavior. This is a basic but acceptable disclosure for a simple retrieval 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?

The description is concise, front-loaded with the purpose, and includes an important usage note and parameter explanation in three short sentences. Every sentence adds value without unnecessary detail.

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 a single parameter, clear usage guidance, and the presence of an output schema, the description adequately covers the essentials. It explains what the tool does, when to use it, and exactly how to obtain the required ID. No additional context is needed.

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 description explains the only parameter report_id as 'Report ID (integer from report_list result)', providing clear meaning and source beyond the schema's bare integer type. This fully compensates for the schema's lack of a description.

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 uses the specific verb 'Get' with the resource 'detailed information about a report/alert by ID', making the tool's function unambiguous. It clearly distinguishes from sibling tools like superset_report_list (listing) and superset_report_create/update/delete (mutations).

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 explicitly states 'if the ID is unknown, call superset_report_list first', providing a clear when-to-use directive and naming the alternative tool. This directly guides the agent on the correct invocation sequence.

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