get_bulletin

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns 'checklist, required forms, and reference code sections,' adding behavioral context. However, it does not mention any side effects, permissions, or rate limits, but given the read-only nature, this is acceptable but not exceptional.

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, each serving a distinct purpose: first explains the action and input, second describes the output. No extraneous words, highly efficient.

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 output schema exists, the description appropriately summarizes return content without redundancy. It covers the core input parameter and output content. Minor improvement would be referencing the sibling 'list_bulletins' tool for context on obtaining IB numbers.

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 provides a concrete example ('IB-121' or '121') for the ib_number parameter, clarifying the expected format. This adds significant meaning beyond the raw schema, though it could be more precise (e.g., regex pattern).

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 explicitly states 'Fetch the full content of a specific information bulletin by IB number' with an example format. It clearly identifies the resource (bulletin) and the action (fetch), distinguishing it from sibling tools like 'list_bulletins'.

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 when to use the tool (when you have an IB number). It provides context for the IB number format but does not explicitly state when not to use it or recommend alternatives like 'list_bulletins' for obtaining IB numbers.

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