find_console_variables

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

With no annotations, the description carries the full burden. It states the tool performs a prefix-search and returns specific data (names, types, flags), but does not disclose whether the operation is read-only, its performance implications, or any side effects. The implementation detail about C++ handler adds minimal behavioral context.

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 covering purpose and pairing context. The third sentence about the language-shim experiment (PR #46) is extraneous for tool invocation and could be omitted for conciseness.

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?

Without an output schema, the description adequately explains the return values (names, types, read-only flags). It also provides workflow context by pairing with related tools. However, it lacks mention of error handling or performance limits beyond the schema's 'limit' parameter.

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?

Input schema has 100% description coverage for both parameters (prefix, limit). The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 it performs a prefix-search on the IConsoleManager registry and returns CVar names, types, and read-only flags. It distinguishes itself from sibling tools like get_console_variable and set_console_variable by focusing on discovery via prefix matching.

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 explicitly pairs this tool with get_console_variable and set_console_variable for discovery workflows, indicating when it should be used. However, it does not mention when not to use it or contrast with other sibling tools like bulk_set_console_variables.

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