Get What Brandon Thinks resources

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description modestly reinforces this with "without fetching external content" and adds the notion of "canonical" resources, but that partially restates the openWorldHint annotation rather than adding new behavioral 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?

A single front-loaded sentence with no filler. It is appropriately sized for a one-parameter read tool, though the trailing "without fetching external content" clause is the only slightly redundant part given the annotations.

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, safe, single-param read tool with annotations covering the safety profile and no output schema, the description is minimally adequate. It could say more about what distinguishes the resource categories to fully guide correct topic 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 description coverage is 0%, so the description must carry the parameter meaning. It enumerates workflow/example/relationship/safety, which corresponds to four of the five enum values, but it omits the "all" default and does not explain what each resource category contains.

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 pairs a clear verb ("Return") with a specific resource ("canonical What Brandon Thinks workflow, example, relationship, or safety resources") and states the scope constraint that no external fetching occurs. It is distinct from the sibling analysis/audit tools, though it doesn't explicitly contrast itself with them.

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?

There is no guidance on when to call this versus the sibling tools (build_chat_analysis_brief, score_interaction_signals, audit_chat_claim) or on prerequisites. The purpose implies a lookup use case but no explicit context or exclusions are given.

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