get_connection_summary

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

No annotations provided. Description indicates 'non-secret' settings, implying no sensitive data returned, but does not disclose idempotency, side effects, or authentication requirements. Basic disclosure, no contradictions.

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?

Single sentence of 9 words, no redundancy. Every word adds value.

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 zero parameters and existence of output schema, description covers essential purpose. Could mention it returns a single object, but output schema fills that gap. Complete enough for a simple info tool.

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?

Input schema has zero parameters, so schema coverage is 100% trivially. Baseline per rules is 4. Description adds marginal value by specifying 'non-secret' nature.

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?

Description clearly states 'Return non-secret Couchbase connection settings for this MCP server.' Verb 'Return' and resource 'Couchbase connection settings' are specific, and it distinguishes from siblings like 'get_document_by_id' and 'run_sql_plus_plus_query' which perform different operations.

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?

Description does not specify when or when not to use this tool, nor does it mention alternatives. For a simple info retrieval tool, this omission is acceptable but missing explicit guidance lowers the score.

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