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

Annotations already declare readOnlyHint and idempotentHint, so no contradiction. The description adds useful behavioral context beyond annotations: authentication is required, and the response exposes a readUrl that is a public anonymous URL for fetching display HTML. This helps the agent understand auth expectations and how to use the result.

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 with no filler. The primary behavior is front-loaded, followed by the group/personal distinction, the readUrl note, and the auth requirement. Every sentence earns its place.

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 read-only retrieval tool, the description covers target selection, authentication, and a notable response field. The output schema covers return structure, and the annotations cover safety/idempotency, so nothing an agent needs to call this correctly is missing.

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%, so the schema already documents all four parameters adequately. The description's group_id guidance mostly repeats the schema description, and it does not add material meaning about slug, access_token, or session_request_id beyond what is already in the schema.

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 states a specific verb and resource: 'Returns the current JSON content and metadata of a data slot by slug.' It also distinguishes personal vs group slots, which clarifies how this getter differs from list_data_slots, set_data_slot, and delete_data_slot.

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?

It gives clear usage context: supply group_id for group slots, omit for personal slots. It also notes authentication is required. It does not explicitly name alternative tools or exclusions, but 'by slug' sufficiently implies this is for retrieving a known slot rather than enumerating slots.

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