Get Default Execution Profile

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

No annotations are provided, so the description carries full behavioral burden. It does disclose the fallback behavior ('Defaults to walletconnect when no explicit default is stored'), which is useful. However, it doesn't state whether this is a safe read operation, whether it requires authentication, or what the return value looks like in detail. For a read-only tool this is partially adequate but leaves gaps.

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?

Two short sentences with zero waste. The primary purpose is front-loaded, and the fallback behavior is stated immediately after, making it 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?

Given no annotations and no output schema, the description should do more to describe the return format (e.g., what an execution profile contains) or any authentication requirements. The fallback default is covered, but completeness is minimally adequate for a tool that returns a non-trivial configuration object.

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 takes zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly avoids doing so.

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?

States a specific verb ('Get') and resource ('stored default execution profile'), clearly distinguishing it from siblings like list_execution_profiles and set_default_execution_profile. It doesn't name those siblings explicitly, but the resource is precise enough that an agent can identify the correct tool.

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 implies usage context ('stored default'), but provides no explicit when-to-use or when-not-to-use guidance relative to alternatives like list_execution_profiles. The sibling set is large, and an agent might be unsure whether to fetch the default profile directly or list all profiles first.

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