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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — it does not explain what 'current knowledge revision' means, whether unpublished drafts are included, or what a missing article returns.

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?

It is a single short sentence, but that sentence is pure duplication of the title, so no information is front-loaded because none is added. Conciseness here reflects under-specification rather than economy.

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?

With no output schema, the description should at least indicate what comes back — the article body plus its current knowledge revision, and how the two relate. For a two-parameter read tool among many closely named siblings, this leaves the agent without enough to disambiguate or call correctly.

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?

Only the company parameter carries a schema description ('Summer company ID'), leaving coverage at 50%; the article slug parameter is documented only through its regex pattern, with no clarification of what a 'guide article' key is or how it differs from a knowledge base identifier. The description contributes zero parameter meaning to compensate for the gap.

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 is a verbatim restatement of the tool title, so it is effectively tautological rather than explanatory. The word 'editable' offers a faint hint that this targets draft/working content rather than published output, but it never contrasts with sibling reads like summer_guides_get or summer_knowledge_get.

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?

There is no when-to-use guidance, no mention of prerequisites (company UUID, article slug), and no routing to alternatives such as summer_guides_get, summer_guides_history, or summer_guides_articles_save. The agent must infer the read-vs-write split from the tool name alone.

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