list-dashboard-services

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

With no annotations, the description carries full burden. It fails to disclose behavioral traits such as pagination (limit, before, after), filtering (include parameter for deleted status), or field selection (fields). The one-line description omits critical information about how the tool behaves.

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?

While very concise (one sentence), the description is under-specified and lacks structure. It does not front-load key information about behavior or parameters. Conciseness is not valuable when it omits necessary details.

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 the complexity of 5 parameters (pagination, filtering, field selection) and no annotations or output schema, the description is completely inadequate. It provides no guidance on how to use parameters or interpret results, making it insufficient for effective tool selection and 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?

Schema coverage is 20% (only fields has a description). The description adds no additional meaning beyond the schema. For a parameter count of 5, the description should explain parameters like limit, before, after, and include, but 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 clearly states 'List dashboard services', which identifies the verb (List) and resource (dashboard services). It is unambiguous, though it does not provide additional context to differentiate from similar sibling tools like list-dashboards or list-database-services.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives (e.g., list-dashboards or get-dashboard-service), nor does it mention prerequisites or context.

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