List properties in a dictionary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the operation is scoped to a single dictionary and supports filtering, but does not elaborate on pagination behavior or return format, which are partially covered by the schema parameters.

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, well-structured sentence that directly states the tool's purpose without redundant detail. It earns its place and is 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?

For a simple list tool with comprehensive annotations and fully documented parameters, the description is sufficient. It clearly communicates the scope and optional filtering. It does not describe return values, but the tool name implies a list of properties, and the schema covers pagination parameters.

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?

The schema provides descriptions for all five parameters (dictionaryUri, limit, offset, searchText, languageCode), so the description does not need to explain each. The mention of 'filtered by text' aligns with the searchText parameter but adds no new semantic information 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's function: listing properties defined by a single dictionary, with optional text filtering. This differentiates it from siblings like bsdd_list_dictionary_classes (which lists classes) and bsdd_get_class_properties (which retrieves properties for a class).

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 clear context for use: to list properties within a specific dictionary, optionally filtered by text. It does not explicitly mention when not to use it or name alternatives, but the intended use case is unambiguous given the tool name and description.

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