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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered. The description adds the useful behavioral constraint that it should be called ONCE (idempotency reinforcement) and lists the content domains. It doesn't describe return size or format, but with readOnly+idempotent annotations the description meets the lower bar without exceeding it.

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 sentences, front-loaded with the core purpose then the timing rule. The enumerated topic list is dense but earns its place as a preview of contents. Minor verbosity in the middle of the list, but no filler sentences.

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 zero-parameter read-only reference doc with no output schema, the description tells the agent what the doc contains and when to consult it. The absence of an output schema means it could hint at whether the return is markdown/JSON, but that's a minor gap given the documented content list.

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?

Zero parameters, so per rubric the baseline is 4. No schema to compensate for and no wasted parameter discussion. Nothing here needs additional explanation.

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 resource ('layout-format reference for Sonar screenshot sets') and enumerates the exact topics it covers (JSON schema, coordinate system, image handling, fonts, translation overrides). An agent can tell it's a reference doc, not an action tool. Loses a point because it doesn't name a sibling alternative (e.g., sonar_create_screenshot_set, sonar_update_screenshot_set) that an agent might confuse it with.

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?

Explicitly says when to use: 'Call this ONCE before creating or editing screenshot layouts.' The 'ONCE' qualifier is valuable timing guidance. Missing an explicit statement of when NOT to call it (e.g., after you already know the schema) or which siblings pair with it.

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