cryptopolitan-mcp

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

No annotations provided, so description carries full disclosure burden. States what it retrieves but omits behavioral traits: whether details are sensitive/cached/static, authentication requirements, or if this is idempotent/read-only behavior.

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 efficient sentence with no redundancy. Every word earns its place—immediately identifies action and target resource without filler.

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?

Adequate for a simple parameterless getter, but lacks specification of what 'connection details' includes (endpoint URLs, authentication tokens, status metadata?). No output schema exists to compensate, leaving return value ambiguous.

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 contains 0 parameters (empty object) with 100% coverage. Description correctly makes no parameter claims. Baseline score applies per rubric for zero-parameter tools.

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?

Uses specific verb 'Get' with clear resource 'connection details' scoped to 'Cryptopolitan MCP server'. Lacks specificity on what 'details' entails (URLs, tokens, status?) but sufficiently clear for selection.

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?

Provides no guidance on when to invoke this tool vs alternatives, prerequisites, or expected calling patterns. No siblings exist, but still lacks contextual guidance on when connection details are needed.

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