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

No annotations are provided, so the description must convey safety and behavior. 'Returns the guide' implies a read-only, safe operation, but it doesn't add details about response format, size, or potential side effects. For a simple parameterless tool, this is adequate but not rich.

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, front-loaded sentence that immediately conveys the key action ('CALL THIS FIRST') and the tool's purpose. No filler words or redundancy.

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 simple guide tool with no parameters and no output schema, the description is sufficiently complete. It states the tool's purpose and scope, though the trailing ellipsis is slightly informal and could be more explicit about what the guide contains.

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 tool has zero parameters, and the schema is fully declarative. The description doesn't need to explain parameters, and the 'CALL THIS FIRST' hint compensates for any lack of schema-level context. Baseline 4 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 tool returns the guide for Delora MCP and outlines what it covers (quotes, chains, tokens, tools). It distinguishes itself from sibling tools by positioning itself as the orientation resource, not the specific data-fetching tool.

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 explicit directive 'CALL THIS FIRST' provides clear when-to-use guidance, informing the agent to invoke this tool before any sibling tools. This is a strong usage signal that differentiates it from alternatives.

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