surprise_research_topic

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

Annotations indicate readOnlyHint=true, which is consistent with the description's 'pick' action being non-destructive. The description adds behavioral context by explaining the sortition sampling method and the purpose of countering bias, going beyond the annotation alone.

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 extremely concise: two sentences with no wasted words. The [Pro] prefix efficiently denotes premium tier, and the content is front-loaded with the core action.

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 tool's simplicity and the presence of an output schema, the description covers the essential aspects: what it does, why to use it, and the key parameter (n). It lacks only a brief note on vault_path, but overall is sufficient for agent understanding.

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 0%, so the description must explain parameters. It mentions 'n random gaps' clarifying the 'n' parameter's role as the count, but does not explain 'vault_path' or its format. Partial compensation for the missing schema descriptions.

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 the tool picks random gaps from the low-priority long tail, using the specific verb 'pick' and resource 'gaps'. It distinguishes itself from siblings like 'list_gaps_by_priority' and 'generate_research_questions' by emphasizing random sampling of low-priority items.

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 provides context for use by noting it breaks confirmation bias and surfaces topics one wouldn't pick themselves. This implies a scenario where the agent wants to explore unexpected areas. However, it does not explicitly state when not to use it or mention alternatives.

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