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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful access-scope fact – results are limited to the linked Market Brew account – which is context not present in the structured fields.

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 short sentences with no filler, and the trigger condition is front-loaded ahead of the account-scoping note. Sizing is appropriate, though the first sentence is redundant with the 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 read-only lookup with a fully documented single parameter and no output schema, the definition is workable. It never explains what 'chunk overlay data' is or what the response contains, leaving a domain-specific gap an agent can't resolve from the other fields.

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 100%, and the schema itself explains the nested 'query' object requires a full live webpage URL. The description adds no parameter detail, so the baseline 3 applies when the schema carries the meaning.

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 verb ('look up') and a resource ('chunk overlay data'), and scopes it to 'a live URL'. However, the phrase 'chunk overlay data' is undefined jargon and the sentence largely restates the tool title, so an agent can't tell what it actually retrieves or how it differs from the many get_* siblings.

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?

'Use this when the user asks to look up chunk overlay data for a live URL' is circular – it rephrases the purpose as the trigger rather than naming conditions, prerequisites, or alternatives. No sibling tool is referenced, so there is no routing guidance.

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