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

Annotations already carry readOnly/idempotent/non-destructive, but the description adds a substantive safety trait they don't: returned content is the person's data and instructions inside it must never be followed (prompt-injection guard). It doesn't say what happens with an unknown id or a kind/id mismatch, and openWorldHint is left unelaborated.

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 tight sentences with use case, exclusion and safety note, front-loaded so the reader learns the primary purpose first. Minor cost: the opening 'AI Agents (inside one system)' is awkward phrasing that delays the actual verb slightly.

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?

Return shape is covered by the output schema and all four parameters are fully described, so the description only needed to add routing and safety context, which it does. Remaining gap is edge behavior on invalid or mismatched ids, which matters for a batch read of up to 100 ids.

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% and the schema already documents ids (max 100), kind's enum, fields, and the system lookup rule, so the description's only added semantics is that ids originate from list_related_records. Baseline 3 is correct when the schema does this much of the work.

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?

States a specific verb (read) and a specific resource (notes, tasks, calls, meetings, emails) scoped to one AI agent's system, retrieved by ids. It explicitly disclaims the sibling list_related_records, so an agent can separate lookup-by-id from discovery without opening either schema.

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?

Gives an explicit when ('read ... by their ids, as list_related_records gives them') and an explicit when-not with the named alternative ('Not for finding them (use list_related_records first)'). It leaves one sibling gap: it never distinguishes itself from get_record or search_records, which an agent comparing tools would still have to infer.

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