get_dashboards

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose the important API limit of 200 dashboards and attributes it to API limits. However, it does not explain whether guid returns a single dashboard, how search and guid interact, pagination behavior, or response shape, leaving meaningful gaps.

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 two short sentences with no filler. The core action and key constraint ('max 200 due to API limits') are front-loaded, and the search guidance is a useful second sentence. Every word earns its place.

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 simple read tool with three optional parameters and no output schema, the description is adequate but incomplete. It misses the relationship with the sibling search_all_dashboards tool and does not clarify parameter interactions such as guid combined with search or limit. An agent could call it correctly, but might not choose the optimal tool.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds a nudge to use search for efficient lookup and gives context for the 200 limit, but it does not add substantive meaning beyond the schema's parameter descriptions.

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 a specific verb and resource: 'Get New Relic dashboards', with a clear scope limit of 200. It does not explicitly distinguish itself from the sibling 'search_all_dashboards', so it misses the top score for sibling 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 implies usage guidance with 'Use search parameter to find specific dashboards efficiently', but it does not say when to prefer this tool over search_all_dashboards, when not to use it, or how to handle the 200-item API limit. The guidance is present but only implied.

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