superset_get_menu

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the menu structure reflects the current user's permissions (variability) and is read-oriented ('Get'), but it does not explicitly state safety (no side effects), authentication requirements, or potential empty responses. It adds some context beyond the name but lacks full transparency.

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 two concise sentences, front-loaded with the main action and followed by a value-adding use case. There is no redundant or extraneous wording—every sentence earns its place.

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 tool's simplicity (no parameters, a likely straightforward output), the description is complete: it states what the tool returns (menu structure) and why it matters (permissions/sections). The presence of an output schema covers return format details, so no further elaboration is required.

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 zero parameters and the schema is empty, so there are no parameter semantics to explain. Per the rubric, 0 parameters earns a baseline 4. The description adds no parameter-related detail, but none is needed.

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 explicitly states the tool gets the 'Superset navigation menu structure,' using a specific verb and resource. It also adds context ('useful for understanding available sections and the current user's permissions') that clarifies the intent and distinguishes it from other Superset tools focused on roles, users, or dashboards.

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 gives clear context on when to use the tool: to understand available UI sections and the user's permissions. While it does not explicitly name alternatives like superset_get_current_user_roles or superset_permission_list, it implies a distinct use case without exclusions, meeting the level for clear context.

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