get_capabilities

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

With no annotations, the description carries the behavioral burden. It discloses return behavior (tool names grouped by category), efficiency (single call is faster), and that it indicates authentication needs. This is solid though not exhaustive; it does not explicitly state that the call is read-only or describe failure modes, but for a capability-discovery tool the provided detail is sufficient.

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 front-loaded with the core purpose and usage instruction, then supplies behavioral detail. It is compact, but 'current auth status' in the first sentence and 'Also shows if authentication is needed' later are mildly redundant, preventing a perfect conciseness score.

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 zero-parameter discovery tool with an output schema, the description covers invocation triggers, return grouping, auth-status behavior, and where to start. Nothing essential is missing for an agent to select and call it correctly.

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?

There are zero parameters and schema coverage is 100%, so the schema already fully documents the input surface. The baseline for zero-parameter tools is 4; the description adds no parameter detail because none is needed.

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 uses a specific verb-resource pair ('Get a full list of all available tools') and adds auth status and getting-started guidance. It clearly differentiates from domain-specific siblings like get_site_details or submit_sitemap by defining its scope as server-wide discovery.

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 an explicit trigger condition: 'ALWAYS call this first when asked what tools are available, what this server can do, or how to get started.' It also gives a rationale (single call vs individual searching), which helps the agent decide when to invoke it instead of alternatives.

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