get_datasets

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

The description discloses what data is returned (DAX command text, fields, query parameters, filters) but does not mention if the operation is read-only, side effects, error handling, or required permissions. Without annotations, the description carries the full burden for behavioral context, and it falls short.

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 that concisely lists the returned data. It is front-loaded with purpose and avoids unnecessary words. However, it could be slightly more structured with bullet points for readability.

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 tool's simplicity (one parameter, no output schema, no annotations), the description provides a reasonable overview of what it does. However, it lacks details on the return format, error behavior, or performance implications, which would be helpful for a complete understanding.

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 has 100% coverage with one parameter ('path') described as 'Absolute path to the .rdl file to read.' The description does not add extra meaning beyond the schema, but the baseline score of 3 is appropriate since the schema already fully documents the parameter.

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 that the tool returns 'Full DAX command text, fields, query parameters, and dataset-level filters for every DataSet in the report.' It uses a specific verb ('get') and resource ('datasets'), and it is well-distinguished from its sibling 'get_dataset' which implies a single dataset.

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 does not provide any guidance on when to use this tool instead of alternatives like 'get_dataset' (which likely retrieves a single dataset) or other dataset-related tools. No prerequisites, limitations, or usage context are mentioned.

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