bdesign_generation_history

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

The annotation readOnlyHint: true already covers the read-only nature. The description adds no additional behavioral detail (e.g., default limit, ordering, or whether it returns all history or recent only). Since no extra context is provided beyond the annotation, the score is low.

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 a single clear sentence with no redundant words. It immediately conveys the core functionality without unnecessary elaboration, making it highly efficient and easy to parse.

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?

There is no output schema, so the description should compensate by explaining what the response contains, pagination, or default behavior. It does none of these. The description is minimal and lacks essential context such as whether the history is ordered, the meaning of 'limit', or any filter options, leaving significant gaps.

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%. The description does not explain the purpose of the 'limit' parameter and only vaguely implies 'projectId' via 'for a project'. With no parameter descriptions and no compensation in the tool description, the agent has insufficient information to correctly populate parameters.

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 the action (List) and the resource (generation history) with a scoping qualifier (for a project). This distinguishes it from sibling tools like bdesign_generation_status (which checks a single generation) and bdesign_generation_submit (which creates a generation), making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as bdesign_generation_status or bdesign_generation_models. There is no mention of conditions, use cases, or differentiators, leaving the agent without context for tool selection.

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