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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior needs no restatement. The description adds that the content is sourced best practices paired with underlying studies, which is useful context. It says nothing about payload size, whether all sections are returned when topic is omitted, or how current the playbook is.

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?

Lead sentence front-loads the verb and the nature of the resource, then the enumeration and usage sentence follow. The long parenthetical list is dense but each gloss carries information; only modest trimming would be possible.

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?

A read-only reference tool with no output schema, so the description must convey what comes back, and it does by naming all nine sections and their intended use. Remaining gaps are the omitted-topic default and whether nested query objects accept anything besides topic, both minor for a static content fetch.

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 0% and the single parameter is a nested query.topic with a nine-value enum, so the description does real work by glossing several topics (target-market = ICPs, buying-signals = what each signal shows and how to act, plays = sequencing guidance, experiments = reading results). However, it says "Pass topic" without noting the query wrapper, and it never states that omitting topic returns every section, which is the key default behavior.

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 verb and resource ("Returns Leadpoet's sourced best practices") and enumerates the sections the payload contains, which lets an agent recognize a static reference/knowledge lookup rather than a data query. It does not explicitly distinguish itself from nearby retrieval siblings such as getGtmContext, getBrief, or getIcp, so differentiation is inferred from content rather than stated.

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?

Gives concrete triggering situations: building or changing an ICP, planning a request or campaign, drafting or reviewing outreach. That is clear when-to-use guidance. It stops short of naming an alternative tool or stating when not to call it.

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