get_mode

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

The annotations already declare this as read-only, idempotent, non-destructive, and not open-world, so the safety profile is covered. The description adds the list of valid modes and the empty-input behavior, but says nothing about return shape or content of a mode guide.

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 very concise and front-loads the tool's topic before listing modes and the empty-value behavior. The long mode list is necessary, and no sentence is wasted, though the opening phrase could be slightly more informative.

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 read-only lookup with no output schema, the description gives enough to invoke the tool with a valid mode or empty value. However, it does not explain what kind of content a mode guide returns or how this tool relates to sibling retrieval tools, leaving selection ambiguity.

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 0%, so the description must carry parameter meaning. It usefully enumerates all valid mode values and explains that an empty value lists all modes, compensating well for the missing schema documentation, though it does not specify case sensitivity or exact matching rules.

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 says 'Working mode guide' and lists possible mode names, but it does not clearly state what the tool retrieves or how a 'guide' differs from sibling tools like get_framework or get_principle. The purpose is inferable but vague and lacks a specific verb+resource framing.

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?

There is no guidance on when to use get_mode versus the many sibling retrieval tools. The only usage note is 'Empty = list all,' which explains parameter behavior rather than tool selection.

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