brain_backlog

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose that the vault scan is bounded, most-recent-first, and adds iCloud latency, plus that it is off by default. However, it does not state whether the tool is read-only, any permission requirements, or other side effects, leaving major gaps.

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 two sentences, front-loaded with purpose, and contains no fluff. Every word adds value, including the technical rationale for the includeVault default.

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?

The description covers purpose and one parameter adequately, but lacks details on output format, how 'repos' interacts, and general usage context. Without annotations or output schema, this leaves some uncertainty for an agent deciding on invocation.

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 compensate. It explains includeVault in detail (default, behavior, latency rationale) but does not describe 'repos' at all, leaving one of two parameters undocumented. This partial compensation earns a mid score.

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 identifies the tool's scope: 'Unified open items across GitHub PRs/issues and local git.' This distinguishes it from sibling tools like brain_where_deploys and brain_db_schema. However, it lacks an explicit verb (e.g., 'list' or 'fetch'), relying on the noun phrase 'open items' to imply the action.

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 implies usage (for viewing open items from GitHub and local git) but provides no explicit guidance on when to use this tool versus siblings, nor any exclusions or alternatives. The main detail is the includeVault parameter behavior, not usage context.

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