card_builder_list_button_toggle_features

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

No annotations provided, so description carries full burden. It discloses that feature IDs are namespaced by domain and that passing domain filters results. It does not mention side effects (none expected) or performance limitations, but is transparent about filtering and naming convention.

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 short and structured with bullet points, front-loading the purpose. Every sentence adds value without redundancy.

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 simple interface (one optional parameter, output schema exists), the description is complete. It explains the key concepts (namespacing, auto value) without needing to cover return values since output schema handles that.

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 has 0% description coverage; the description adds full meaning for the single parameter 'domain'. It explains it filters by domain, gives examples of feature IDs, and explains the 'auto' value. This goes far beyond the schema.

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 tool lists feature IDs for block-button-toggle/block-select-menu. It distinguishes from sibling card_builder tools by being specific to this block type, using a specific verb 'List' and resource 'feature IDs'.

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 explains when to use: to get feature IDs for those blocks. It mentions filtering by domain and omitting to see all. It provides context like the 'auto' default. While no explicit when-not-to-use, the usage is clear.

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