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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses a privacy stance: 'This server never requests your campaign or threat-intel notes and instructs your AI to keep them local.' It also explains content-scoping behavior (some topics defer to another tool), which is useful context.

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?

The description is long but front-loaded with the core purpose. The enumeration of topics is dense and could be structured with bullets, but every sentence carries useful information. The privacy note is a slight tangent but valuable.

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?

Given the 17 enum topics, 2 parameters, and no output schema, the description is remarkably complete. It covers all topic meanings, the deferral behavior, parameter pairing, and a privacy guarantee. This fully equips an agent to select and invoke the tool 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?

Schema coverage is 100%, but the description adds significant meaning to the enum values (e.g., 'attribution (full Six Signals prose)', 'confidence (ICD-203 ladder)', 'pyramid_of_pain') and clarifies the relationship between topic and field_id. It also states that 'field_id' is 'Only meaningful with topic='fields'', reinforcing 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?

The description clearly states 'Get Lenny Zeltser's expert CTI writing guidelines' with a specific verb and resource. It distinguishes itself from siblings by explicitly deferring general writing topics to `get_security_writing_guidelines` and enumerating CTI-specific topics.

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?

The description gives explicit guidance on when to use this tool vs the alternative: 'The general writing topics ... now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics.' It also instructs pairing 'fields' with field_id, and notes default behavior when topic omitted.

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