tb_get_dashboards

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not explain that the required 'device_id' implies dashboards are scoped to a device, nor does it mention any read-only nature, pagination, or output format. It is essentially a label.

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 with no waste, but it is under-specified. It is concise but lacks needed detail about the device_id relationship, making it borderline under-specification rather than ideal conciseness.

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?

Despite being a simple tool, the description is incomplete. It fails to explain why 'device_id' is required, what dashboards are returned, or any filtering semantics. With no output schema or annotations, the description should provide more context for correct invocation.

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 describes 'device_id' as 'ThingsBoard server device ID' giving 100% coverage. The description does not add any further meaning, so the baseline of 3 applies.

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 'List dashboards from ThingsBoard' is clear and specific: it identifies a particular resource (dashboards) and the platform. It distinguishes itself from all sibling tools, none of which mention 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?

No guidance is provided about when to use this tool versus alternatives. There are no prerequisites, no alternative tool comparisons, and no context like 'use this to see all dashboards for a device'.

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