read_theme

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

With no annotations provided, the description carries the burden of disclosing behavior. It clearly lists the returned components and notes the inclusion of the full theme JSON, effectively communicating what the tool does. It does not explicitly state 'read-only' but the verb 'read' adequately conveys non-mutation.

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 exceptionally concise: two sentences that front-load the purpose and then list the detailed contents. Every word is informative with no redundancy.

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 operation with a single parameter and no output schema, the description adequately explains what will be returned. It does not elaborate on potential edge cases or return format specifics, but the core information is present and sufficient for most use cases.

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%, and the description does not explain the reportSessionId parameter. While the parameter is self-explanatory in context, the description fails to add any meaning beyond the schema, leaving the parameter undocumented.

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 a specific action ('Read') on a specific resource ('the report's current custom theme') and enumerates the exact contents returned (name, palette, structural colours, visualStyle defaults, full JSON). This distinguishes it from the many set_theme_* siblings which modify theme components.

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 the tool is for inspection or to obtain the theme for re-application, giving clear context for when to use it. However, it does not explicitly name alternatives or state when not to use it, though the read-only nature is evident from the verb.

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