get_server_info_authenticated

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

The description states 'retrieve', suggesting a read-only operation, but annotations declare readOnlyHint=false, indicating the tool may not be read-only. This is a direct contradiction. The description does not disclose any behavioral traits beyond what the annotation already provides, and the contradiction undermines transparency.

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 sentence with no filler, but it lacks structure such as bullet points or separate sentences for different aspects. It is efficient for its length, but could be more informative without added verbosity.

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?

The description provides basic context (auth requirement for third-party versions) but omits details about what the 'extra server version information' includes, especially since there is no output schema. Adequate for a simple tool but incomplete given the lack of return value documentation.

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 100% as both parameters have descriptions. The tool description adds no additional meaning beyond the schema, only mentioning 'using supplied credentials'. Baseline score of 3 is appropriate.

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 'Retrieve' and the resource 'extra server version information', with a specific qualifier 'using supplied credentials (for third-party system versions)'. This distinguishes it from the sibling tool get_server_info which likely does not require authentication.

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 authenticated credentials are needed for third-party system versions, but does not explicitly state when not to use it or contrast with get_server_info. The context is clear but lacks explicit exclusions or alternatives.

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