bb_status

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

With no annotations and no output schema, the description carries the full behavioral burden. It lists content categories but never confirms this is a non-mutating read (vs. something that triggers a sync/authenticates), says nothing about auth state needed, rate limits, or how stale the status might be — notable given the adjacent bb_sync and bb_sync_status tools that do act.

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 compact sentence with no filler, listing the three payload areas up front. It reads as a fragment rather than a complete sentence, but nothing is wasted.

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 zero-parameter status tool with no output schema, the description does sketch the returned categories, which is useful. However, it omits the read-only guarantee and any differentiation from bb_sync_status, leaving ambiguity that a status tool's description should resolve.

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 takes zero parameters, so the schema-based baseline of 4 applies. No parameter meaning is required from the description, and none is offered or needed.

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 enumerates what the tool reports (Blackboard instance, account, download path, last sync time), which hints at a read-only status/info query, but it never states a verb or that it 'returns' anything — it is a bare noun phrase. It also fails to distinguish itself from the sibling bb_sync_status, which sounds nearly identical in scope.

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 when-to-use context, no prerequisites, and no routing between this tool and bb_sync_status or bb_login. The agent must guess from the field list alone whether to call this or the closely-named sibling.

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