List your MCP profiles

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts — an API key is required and results are scoped to the caller's own saved profiles — but says nothing about ordering, volume, or what an empty result means.

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?

A single clause of about ten words, with the auth prerequisite front-loaded and no filler. It is efficient, though so terse that it borders on under-specification rather than true conciseness.

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 no output schema and no parameters, the description carries the burden of explaining what comes back, yet it only says 'your saved profiles' without describing fields, count limits, or ordering. The auth requirement is covered, but an agent still cannot predict the response shape.

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 there is nothing for the description to disambiguate; baseline 4 applies. The added note that no filtering is possible ('only your saved profiles') is a small bonus that clarifies the absent-parameter behavior.

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 title ('List your MCP profiles') and the phrase 'returns only your saved profiles' together convey that this enumerates saved profiles, but the description itself never states a verb+resource pairing like 'Lists your servers/profiles'. It also does nothing to distinguish this from sibling list tools such as list_directories or list_connections.

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?

'Returns only your saved profiles' implies a scope boundary (no other users' profiles, no filtering options), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling tool. The agent must infer that this is the discovery call before create_server or get_account.

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