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

With no annotations, the description carries the full behavioral burden. It usefully explains view contents and the effect of full: true for task and ledger, and implies read-only access through 'Look at' and key ownership through 'mine', but it omits permissions, pagination, rate limits, error behavior, and an explicit read-only statement.

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 one long pipe-delimited sentence with nested parentheticals. It is not bloated with irrelevant content, but the run-on structure makes it harder to scan than a cleanly front-loaded or bulleted definition.

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 tool has four parameters, no annotations, no output schema, and 0% schema description coverage, so the description must do substantial work. It adequately describes the available views and optional parameters, but leaves out operational details such as authentication requirements, pagination, return shape, and failure modes.

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 description coverage is 0%, so the description must compensate, and it largely does: it explains all eight what values, notes that kind narrows offers, indicates id reads a specific showcase page or task, and explains full for task and ledger. It does not fully clarify that id applies only to certain views or restate that what is required, but the semantic coverage is strong.

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 that the tool looks at the Bureau and enumerates eight specific views (offers, kinds, showcase, open, task, mine, ledger, usdc), making the resource scope clear. The verb 'Look at' is vague and the description does not distinguish this tool from siblings such as bureau or workshop_look, so it falls short of a 5.

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 enum-value descriptions imply which view to use for specific needs, such as offers for sale listings or task for a specific deliverable. However, there is no explicit guidance on when to use this tool versus sibling tools, no exclusions, and no prerequisites beyond the implied key context in 'mine'.

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