remote_profile_get

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait: 'secrets redacted,' which informs the user about output sanitization. However, it does not disclose other behaviors such as error handling when the profile does not exist or any permission requirements. This is a minimal but relevant disclosure.

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, front-loaded sentence with no wasted words. It conveys the action, object, and key detail (redaction) efficiently.

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 one-parameter read tool, the description covers the core purpose and a key output trait. However, it omits any mention of error conditions (e.g., not found) or prerequisites. The existence of an output schema reduces the need to describe return values, but the description is still basic and leaves some 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 input schema has only one parameter, 'name', with no description. The tool description says 'one saved connection profile,' which implies that 'name' identifies the profile, but it is not explicitly stated. Since schema description coverage is 0%, the description partially compensates but could be more explicit about the parameter's meaning.

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 the action ('Read') and resource ('one saved connection profile'), with a scope ('one') that distinguishes it from sibling tools like remote_profile_list (which lists all profiles) and remote_profile_create (which creates). This is a specific and unambiguous purpose.

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 when you need a single profile by name, but it does not explicitly mention when to use this tool versus alternatives like remote_profile_list. No exclusions or alternative references are provided, so guidelines are only implied.

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