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

Discloses a non-obvious side effect beyond the annotations: 'the summary and tasks are written on first read', which explains why readOnlyHint=false on a nominally read tool. This is exactly the kind of context annotations alone cannot convey. It stops short of saying whether the write is idempotent or whether it costs quota/rate limits.

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?

Two tight sentences, both front-loaded with the most decision-relevant information (what is returned, then the lazy-write behavior, then the key's provenance). No filler and nothing redundant with the schema or title.

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 7-parameter tool with zero schema coverage and no output schema, the description covers only themeKey and the write-on-read nuance. Nothing conveys what the optional date range and engine filters do, or what the returned quotes/tasks look like beyond their names, so an agent cannot call this confidently outside the happy path.

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% across 7 parameters, so the description must carry the load; it only explains themeKey's origin. The from/to window, engine vs engines (single vs array, max 10), projectId, and siteId are entirely undocumented in both places, leaving the agent to guess the filtering 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?

States a specific verb and resource: 'Read one sentiment theme with quotes and suggested tasks.' That distinguishes it from get_ai_sentiment_overview and get_ai_sentiment_benchmark by scoping to a single theme. It does not explicitly name those siblings as alternatives, keeping it short of a 5.

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 workflow by saying themeKey comes 'from the AI sentiment overview', which tells the agent this is a drill-down after the overview. It does not state any when-not-to-use condition or contrast with the benchmark/overview siblings, so guidance is implied rather than explicit.

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