get_reports

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

No annotations provided, so description carries full burden. Explains return values, error cases (workspace ID not found, permission errors, empty list), and implies read-only behavior. Transparent about behavior beyond basic purpose.

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?

Well-structured with sections for parameters, returns, examples, and error handling. Some redundancy (e.g., 'Returns report information including' and later list), but mostly concise and front-loaded with main action.

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 no annotations and low schema coverage, description compensates well. Explains return fields, error handling, and usage. Output schema exists but not shown; description covers return values. Could include more details on auth requirements or rate limits.

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?

No input schema descriptions (0% coverage), but description fully explains each parameter: workspace_id optional (default My workspace), format options (json/markdown), detail levels (concise/detailed). Provides usage examples that clarify semantics.

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?

Clearly states it gets PowerBI reports from a workspace, listing specific return information (report name, ID, URLs, dataset ID). Distinguishes from siblings like get_dataset (which gets a single dataset) and get_workspaces (which lists workspaces).

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?

Provides useful context: 'Useful for discovering available reports and getting report URLs.' Includes example usage and error handling scenarios. However, does not explicitly state when not to use or alternatives.

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