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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description goes further by enumerating what comes back (definition, why it works, when it backfires, ad examples, related/opposite techniques, citable link), which is real behavioral value beyond the structured fields.

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?

Front-loaded with the what and the identifier forms, then a single usage sentence with no filler. The return-value enumeration is a long clause but it carries information since there is no output schema.

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 correctly compensates by describing the payload, and the annotation set covers safety. The one gap is silence on the optional category parameter and its comparison behavior, which the schema documents on its own.

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%, so both parameters are already documented and the category comparison behavior lives in the schema. The description adds only the concrete PT-ID format example ('PT-PRV-10000'), and notably never mentions the category parameter at all, so it stays at the baseline.

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 (look up) and resource (one persuasion technique) plus the accepted identifier forms (PT-ID, slug, exact name). It reads as a single-record retrieval tool, clearly separable from the sibling find_persuasion_techniques, which is exploratory search.

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 triggers: use before applying or recommending a technique, and whenever someone asks what a tactic is called or how it works. It sets context well but never names the discovery alternative (find_persuasion_techniques) or states when this lookup is the wrong choice.

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