Platform docs

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

No annotations are provided, so the description carries the burden. The description does disclose that calling without a topic lists topics, which is a behavioral trait not derivable from the schema. However, it doesn't disclose the return format, whether content is paginated, or the depth/format of the documentation returned. For a read-only docs tool this is acceptable but could be richer.

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?

Two sentences, zero waste. The first sentence establishes purpose and topic domains; the second sentence gives the key usage behavior for the optional parameter. Every word earns its place and the most important operational detail (call without topic to list) is front-loaded into the second sentence.

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?

Given a simple single-optional-parameter tool with 100% schema coverage and no output schema, the description is fairly complete. It identifies the pain-point domains and the zero-argument behavior. A minor gap: it doesn't specify what the documentation content looks like when called with a topic, but the schema enumerates topics clearly. For the complexity level, this is sufficient.

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 description coverage is 100%, so the topic parameter is fully documented in the schema with its allowed enum values. The description adds the behavioral detail that omitting the topic lists available topics, which complements the schema. Since the schema does the heavy lifting on parameter meaning, baseline 3 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 this is a docs tool for platform pain points (signing, dev mode, packaging, pairing) and distinguishes its purpose by noting it covers deep documentation topics. However, it doesn't explicitly differentiate from sibling tools list_devices and connect_device, though the context makes it fairly obvious docs is informational. The verb 'deep docs' and specific pain points give a clear, specific purpose.

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 without a topic to list topics,' which is a clear usage guideline for the zero-parameter case. It gives some guidance that topics map to specific pain points (signing, dev mode, packaging, pairing), though it doesn't explicitly state when NOT to use this tool versus alternatives like connect_device. The sibling tools are operational (list/connect), so context implies docs is for reference, but that contrast is not stated.

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