list_bulletins

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

No annotations provided, so description carries full burden. Only states it lists bulletins, with no mention of behavioral traits such as read-only nature, authentication requirements, or rate limits. No contradictions.

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?

Two concise sentences with no wasted words. First sentence states purpose and optional filtering, second provides useful context on what bulletins are.

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?

Incomplete for a tool with 2 parameters and no parameter descriptions in schema. Does not mention the 'limit' parameter or any pagination/format details. Output schema exists but return structure not discussed.

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%. Description adds meaning to 'project_type' with examples, but completely omits the 'limit' parameter. Fails to compensate for lack of schema documentation.

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?

Clearly states the action (List), the resource (Development Services Department information bulletins), and optional filtering by project type with examples. Distinguishes from sibling 'get_bulletin' which likely retrieves a single bulletin.

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?

Implies usage for listing bulletins, optionally filtered. Provides an example of filtering by project type. However, no explicit guidance on when not to use or how it differs from siblings like 'search_municipal_code'.

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