Open-Brain

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

No annotations are provided, so the description carries the full burden. It mentions 'resurface' which suggests a read operation, but doesn't disclose behavioral traits such as whether it modifies data, requires authentication, has rate limits, or what the output looks like. The description adds minimal context beyond the basic action, leaving key operational details unclear.

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 a single, compact sentence that directly states the tool's purpose without fluff. It's front-loaded with the main action ('Resurface forgotten high-quality thoughts') and uses specific terms efficiently. However, the phrase 'across rediscovery/orphan/underrepresented/echo slots' is somewhat jargon-heavy and could be clearer.

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 complexity implied by terms like 'rediscovery/orphan/underrepresented/echo slots', no annotations, and no output schema, the description is incomplete. It doesn't explain what these 'slots' are, how the tool operates, or what results to expect. For a tool with no structured support and potentially nuanced behavior, more detail is needed to guide effective use.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't discuss parameters, which is efficient. Baseline is 4 for zero parameters, as it avoids unnecessary information.

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 states the tool 'resurface forgotten high-quality thoughts' which gives a general purpose, but it's vague about the mechanism ('across rediscovery/orphan/underrepresented/echo slots') and doesn't clearly distinguish it from sibling tools like 'review_stale' or 'weekly_review' that might also resurface content. It specifies a verb ('resurface') and resource ('thoughts') but lacks specificity about what makes this tool unique.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description mentions 'rediscovery/orphan/underrepresented/echo slots' which implies some context, but it doesn't state when this tool is preferred over siblings like 'review_stale' or 'deep_search'. There's no mention of prerequisites, exclusions, or comparative use cases.

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