workspace_conf_get_keys

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

Annotations include readOnlyHint=true, indicating the operation is read-only. The description aligns with this by saying 'Return configuration.' However, it adds no further behavioral disclosures beyond what the annotation already provides (e.g., no mention of rate limits, data size limits, or retrieval behavior).

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, concise sentence that conveys the core purpose without unnecessary words. It is front-loaded and efficient.

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?

With an existing output schema, the description need not detail return values, but it could clarify that it returns key-value pairs for workspace configuration. The description is minimal but sufficient for a simple lookup tool. However, it lacks context about what 'configuration' encompasses (e.g., workspace-level settings).

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 100% and the schema already provides a detailed explanation for the 'keys' parameter, including the expected body format. The tool description adds no additional semantic information beyond what is in the schema. Baseline 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?

Description states 'Return configuration for a specific set of keys.' It clearly specifies the verb and resource, distinguishing from sibling tools like workspace_conf_get_status (which likely returns overall status) and workspace_conf_set (which modifies). However, it could be more explicit by stating it retrieves the values of the specified configuration keys.

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. It does not mention that this tool is for batch lookups of specific keys, nor does it contrast with workspace_conf_get_status or workspace_conf_set. No when-to-use or when-not-to-use information is given.

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