Topical Strategy — topical mapping guidelines

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that records contain inlined content (v7) and that the 'inline' parameter controls metadata-only output. However, it does not disclose other traits like pagination, result size limits, or error conditions.

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 with minimal waste, though the first sentence essentially repeats the title. The second sentence provides the core behavioral information. Could be slightly more concise by merging or removing redundancy.

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 simple tool with one optional parameter and no output schema, the description is minimally adequate: it explains the return type and the parameter's effect. However, it lacks context about what 'records' represent, the meaning of 'topical mapping guidelines', and any assumptions about data volume or structure.

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 schema description ('false → metadata-only (legacy v6 shape)') already explains the inline parameter. The tool description adds 'v7 payload contract' context but does not significantly extend parameter understanding beyond the schema.

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?

Description states 'Returns records WITH inlined content (v7 payload contract)', which clarifies the output format, but the primary purpose of retrieving topical mapping guidelines is only implied by the title. It doesn't explicitly state what the tool does (e.g., list, retrieve, generate) and lacks differentiation from sibling preset tools.

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?

No guidance on when to use this tool versus alternatives like gkb_preset_forbidden or gkb_preset_quality. The description does not mention context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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