list_dashboards

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

No annotations are provided, so the description must carry the full burden. It claims 'max 100 results by default', but the input schema shows a limit parameter with default 1000, a serious contradiction. Additionally, it omits behavioral traits like pagination, caching, and the effect of force_refresh.

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 sentence, which is concise, but it contains a factual contradiction (max 100 vs schema default 1000). The contradiction wastes the agent's trust.

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?

For a listing tool with 8 optional parameters, no annotations, and no output schema, the description fails to cover return format, pagination, or the meaning of repository fields. The contradictory limit reduces completeness.

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 adds meaning for three parameters (solution, name, path_contains) by indicating they are search fields. However, it ignores five other parameters including limit (with contradictory info) and repository fields. The misleading limit statement further reduces value.

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 it lists 'Microsoft Sentinel dashboards', providing a specific verb and resource. It is distinguishable from sibling tools like list_workbooks, but lacks explicit differentiation.

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 mentions search capabilities (by solution, name, or file path), implying usage to find dashboards, but gives no guidance on when to use this tool over other list_* tools or any exclusions.

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