list_beliefs

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

With no annotations, the description must carry the behavioral disclosure burden. It only states 'List beliefs' with filters, but does not mention if the operation is read-only, has pagination, ordering, or any side effects. The output format is not described despite output schema existing.

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 short and front-loaded with the main purpose. The argument list is clearly formatted. No extraneous text, but could be slightly more structured with a brief note on return value.

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?

Lacks information about return format, ordering, or limits. With siblings like deep_search and search, an agent needs more context to choose correctly. Output schema exists but is not referenced.

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 description adds needed meaning. It explains status filter values ('IN', 'OUT', empty) and project fallback to default. However, it does not clarify what 'IN' and 'OUT' represent in terms of truth values.

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 'List beliefs in the knowledge base', using a specific verb and resource. It distinguishes from siblings like get_belief (single) and search (query-based).

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 when-to-use or when-not-to-use guidance. The description implies listing all beliefs with optional filters, but does not compare with alternatives like search or list_entries.

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