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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates the tool returns capability information and implies a read-only action via the verb 'list,' but it does not explicitly state that it is side-effect-free, describe the return format, or mention any prerequisites beyond calling it first. This is adequate but not rich in behavioral detail.

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 two sentences long, front-loaded with the core purpose and followed by a practical usage instruction. Every sentence contributes value with no redundancy or filler, making it highly concise and well-structured.

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 tool with no output schema, the description adequately covers what the tool does, the scope of capabilities, and when to call it. It could be slightly more explicit about the output format (e.g., whether it returns a list or instructions), but the description sufficiently conveys the tool's role as an entry point.

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 input schema has zero parameters, which sets a baseline of 4. The description does not need to explain parameters since there are none, and it adds no parameter-related semantics beyond what the schema already provides.

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 tool lists Spocal MCP capabilities, specifying both sports data tools and the article authoring workflow. It distinguishes itself from siblings by positioning itself as the first call to learn how to embed matches, players, and prediction markets, making the purpose specific and actionable.

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 explicitly says 'Call this first,' providing clear when-to-use guidance for discovering capabilities and workflows. However, it does not explicitly mention alternatives or when not to use this tool relative to sibling tools like list_supported_competitions, so it lacks full exclusionary guidance.

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