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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds helpful context about the output content—configuration guides and the tool list—but does not disclose additional behavioral details such as external lookups or caching.

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?

A single, well-structured sentence that front-loads the verb and resource, then adds the key deliverable content. No filler or redundant phrasing exists; 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?

For a zero-parameter, read-only tool with an output schema present, the description is sufficiently complete. The agent knows what the tool returns, what it is for, and that no arguments are required. Sibling differentiation is adequate given the explicit AI-client connection focus.

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 accordance with schema coverage of 100%, so the schema fully documents what the agent needs to know. The description appropriately focuses on the tool's purpose rather than parameters, and no further parameter elaboration 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 the specific verb 'Retrieve' and names a clear resource: integration and transport configuration guides for connecting the oracle to AI clientsasi as Claude Desktop, Cursor, and MCP clients. It also distinguishes itself from sibling tools by mentioning the complete tool list and capabilities rather than generic oracle info or status.

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 provides clear context about when to use the tool: when the agent needs connection guides for AI clients or the complete accessible tool list. It does not explicitly name alternatives or exclusions, but the stated purpose is specific enough to imply the correct usage scenario.

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