get_user_config

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

Discloses that the tool creates the config file with defaults if it does not exist, an important side effect for a 'get' operation. However, with no annotations, additional details like error handling or authorization needs are omitted.

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?

Three tightly written sentences: first states purpose, second adds content details, third provides alternative and side effect. No wasted words; structured to front-load key information.

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 zero parameters and an existing output schema, the description covers the tool's purpose, return content, alternative tool, and critical side effect. No obvious 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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter information, which is appropriate since none exist.

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 returns the full Metis user configuration from user-config.yaml, specifying the content (research interests, data sensitivity, etc.). It distinguishes from the sibling get_user_profile by contrasting the full config vs a lightweight profile.

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?

Explicitly advises when to use this tool vs get_user_profile, stating 'For a lightweight profile summary...use get_user_profile() instead.' This provides clear guidance on tool selection.

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