ble_read_descriptor

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

No annotations provided, so description carries full burden. Only states action without side effects, permissions, or limitations. Does not disclose if read is idempotent or safe, or whether it triggers any BLE interaction beyond reading.

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: first states action, second gives prerequisite and context. No unnecessary words. Efficient and front-loaded.

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?

No output schema, but description omits return value details (type, format, size). Missing error or edge case info (e.g., invalid handle). For a moderately complex BLE tool, this is incomplete.

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 50%; description only adds meaning for 'handle' (repeats schema). 'connection_id' gets no description. No additional format, constraints, or example values beyond what schema 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?

Clear verb+resource+method: 'Read a GATT descriptor by handle'. Distinguishes from sibling tools like 'ble_read' (characteristic) and 'ble_write_descriptor' (write). Also explains descriptor purpose (metadata like CCCD).

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?

Explicit prerequisite: 'Use ble.discover to find descriptor handles.' Provides context on what descriptors are for. Doesn't explicitly mention alternatives, but sibling tool names imply when not to use (e.g., write vs read).

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