obs_grafana_datasources

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

With no annotations, the description must carry behavioral disclosure. 'List' implies a read-only operation, but the description does not state whether a connection/session is required, whether it returns only the current session's datasources, or any other side effects.

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?

One short sentence with no filler; the action and resource are front-loaded. This is appropriately concise for such a simple tool.

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?

The tool is simple and has an output schema, so return values need not be documented. However, the description omits any mention of session_name, connection prerequisites, or when this tool is the right choice, leaving meaningful gaps for an agent.

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 only parameter, session_name, has no description in the schema (0% coverage) and is not mentioned in the tool description. The title and default value offer minimal clues, but the description adds no meaning to help an agent decide whether to pass it.

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 uses the specific verb 'List' and the resource 'Grafana datasources,' making the tool's primary function unambiguous. It does not explicitly contrast with sibling tools, but the resource name is distinct enough from obs_grafana_alerts and the query tools.

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?

There is no guidance about when to call this tool rather than obs_grafana_alerts, obs_query_metrics, or other siblings, and no mention of prerequisites such as an active session. The agent must infer the tool's niche solely from its name.

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