list_dashboards

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

No annotations are provided, so the description carries the full burden. It says 'List all' but includes a limit parameter (default 50), which creates ambiguity about whether the result is truly all dashboards or truncated. It does not explicitly state read-only behavior or pagination details, though the listing action implies it.

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, compact sentence that is front-loaded with the core purpose and includes useful output details. Every word earns its place without 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?

The tool is simple with one optional parameter and no output schema, so the description covers the basic purpose and return fields. However, the 'all' vs limit discrepancy and lack of pagination details leave gaps that an agent might need to know, such as whether the limit can cause partial results.

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 schema has 100% coverage for the single parameter (limit), so the description adds no additional meaning beyond the schema. Baseline of 3 is appropriate because the parameter is already well-documented in the input schema.

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 a specific verb ('List') and resource ('PostHog dashboards') and clarifies scope ('in the project'). It also distinguishes itself from siblings like get_dashboard by indicating it lists multiple dashboards and states the returned fields (names, IDs, widget counts).

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 implies usage through its clear purpose but provides no explicit guidance on when to choose this over alternatives such as get_dashboard. No exclusions or alternative references are mentioned, only the implied context of listing dashboards.

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