list_dashboard_services

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

The description only says 'list', implying a read-only operation, but provides no details about pagination (despite limit/offset parameters), filtering, or the effect of 'include_deleted'. Without annotations, the description fails to disclose essential behavioral details.

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 concise (three words) but at the cost of informativeness. While it is front-loaded, it sacrifices necessary context for completeness.

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?

With 4 parameters, no output schema, and no annotations, the description is severely incomplete. It lacks essential context about parameter behavior, return format, and edge cases.

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 no meaning beyond the parameter names and types in the schema. With 0% schema description coverage, the description should explain parameters like 'fields' and 'include_deleted', but it does not.

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 states 'List dashboard services', which clearly identifies the verb (list) and the resource (dashboard services). It distinguishes from siblings like 'list_dashboards' and 'list_database_services' by specifying the resource type.

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 on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or comparison to similar list tools.

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