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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds that this is instructional content organized by topic, but says nothing about response shape (e.g., whether it returns a long document) or size, which matters for a guide-fetching tool.

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?

Purpose is front-loaded in the first clause and each topic gets one compact clause, with no filler. The telegraphic phrasing ('topic figures: the figure kit's rules...') is dense but still parseable.

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 single optional enum parameter with full schema coverage and no output schema, the description covers what an agent needs to select a topic. Minor gaps are how the guidance is returned and whether all topics can be retrieved in one call.

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 coverage is 100% and the enum is self-documenting, but the description goes beyond the schema by explaining what each topic actually contains (lesson Markdown form, labels, AI declaration, version checks; figure kit rules, tokens, components; 3D/molecules/physics). That meaningfully helps an agent choose the right topic.

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 states the resource concretely (writing guidance for the commons at ai.page/c/) and enumerates the three topical scopes, which lets an agent separate it from action siblings like save_page or submit_version. The verb is only implied ('how to write'), but the doc-retrieval nature is clear.

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?

Usage is implied: consult this before authoring a topic, and pick a topic based on whether you need base formatting, figures, or advanced figures. There is no explicit when-to-use/when-not statement and no reference to the sibling tools that consume this guidance.

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