get-sdk-docs

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

No annotations provided, so description must disclose behavior. It implies read-only retrieval of documentation but doesn't explicitly state side effects, authentication needs, or rate limits. Minimal transparency for a tool with zero annotations.

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?

Three sentences, front-loaded with purpose, content summary, and usage guidance. No redundancy or unnecessary detail. Efficient 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?

Adequate for a simple documentation tool: covers parameters (via schema) and output nature. But lacks error handling details, and given sibling overlap, could be more explicit about when to use this vs. other tools. Output format not described beyond general content types.

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?

Schema coverage is 100% with descriptions for all parameters. Description adds value by suggesting initial topic values and explaining the purpose of currency and salesChannelId (price formatting, personalization). Exceeds baseline of 3.

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?

Clearly states it gets SDK documentation for a topic and describes content (setup, API usage, etc.). Suggests starting points but doesn't explicitly differentiate from siblings like get-code-example or get-critical-rules, which may cause overlap confusion.

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 sequential guidance ('Start with setup or critical-rules') but lacks when-not-to-use or comparisons to sibling tools. Implicit use case but no exclusions.

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