get_report_settings

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

With no annotations provided, the description carries the full burden. It proactively discloses 'READ-ONLY' (non-mutating), 'decoded to plain values' (transformation behavior), and the conditional 'when one is applied' for the theme name. It does not cover error cases or prerequisites, but the core behavioral traits are well communicated.

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 sentences, front-loaded with 'READ-ONLY read-back', and every phrase adds value. It is concise without losing necessary detail.

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 low complexity (single parameter, no output schema), the description covers purpose, behavior, and the relationship to set_report_settings. It notes the return includes decoded settings and optional theme name, which is enough for an agent to understand what to expect. A short example or error note would push it higher, but it is not incomplete.

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 description coverage is 0%, so the description must compensate. It says 'report-level' but never explicitly explains the reportSessionId parameter, its format, or how to obtain it. The parameter name is somewhat self-explanatory, but the description adds no direct clarification.

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 the tool is a read-back of report-level behavior toggles (config.settings) that set_report_settings writes, and it mentions the added custom-theme name. This verb+resource clarity distinguishes it from siblings like read_theme or get_report_filters.

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 phrase 'The read partner of set_report_settings' explicitly frames when to use this tool: to read back exactly the settings that set_report_settings writes. It does not list exclusions or alternatives, but the pairing with set_report_settings gives clear contextual guidance.

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