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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that results are 'structured narrative and principle records' for the chosen section, with no mention of size, pagination, or fallback behavior when a section is empty.

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, front-loaded with the usage trigger, with no filler. The second sentence partially restates the content list from the first, a small 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?

A single optional enum parameter, full schema coverage, annotations covering the safety profile, and an output schema mean the description needn't explain return shape. It is complete enough for an agent to call correctly, with only marginal room to clarify section selection.

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 values are documented in the schema. The description loosely maps content concepts to those values ('personal letter, architectural story' → story; 'core operational tenets' → principles), which is mildly useful but not a precise enum-to-meaning mapping.

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 resource (Zain Ahmed's about content: philosophy, personal letter, architectural story, operational tenets) and what it returns ('structured narrative and principle records'). The content is clearly distinct from sibling tools like get_profile or get_projects, though the description never explicitly names those siblings.

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?

Opens with an explicit trigger ('Use this tool when you need...') listing the content types that select this tool. It provides clear usage context but no when-not guidance or named alternatives, which keeps it short of a 5.

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