get_dashboard_lists_manual

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Fetch') but doesn't specify authentication needs, rate limits, error conditions, or what the output looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 single, efficient sentence with no wasted words, clearly front-loading the core action and resource. It's appropriately sized for a simple fetch operation with no parameters.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is minimal but inadequate. It lacks details on authentication, output format, error handling, or how to specify which dashboard list to fetch, making it incomplete for reliable agent use despite low complexity.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it implies the tool fetches a specific dashboard list without specifying how it's identified (e.g., by ID), slightly hinting at implicit context. Baseline 4 is correct for zero parameters.

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 action ('Fetch') and resource ('an existing dashboard list's definition'), making the purpose specific and understandable. It distinguishes from sibling tools by focusing on a single dashboard list rather than listing multiple or performing other operations, though it doesn't explicitly contrast with similar 'get' tools like 'get_dashboard_lists_manuals'.

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 provides no guidance on when to use this tool versus alternatives, prerequisites, or context. It mentions 'existing' but doesn't specify how to identify which dashboard list to fetch or differentiate from other retrieval tools in the sibling list, leaving the agent with insufficient usage context.

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