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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description only needs to add context beyond that. It does so by specifying the org_not_linked error condition and the guardrail 'do not invent join_org,' which are genuinely useful behavioral details. No contradiction with the annotations exists.

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?

The description is very compact: three sentences each earn their place. The first states the core purpose, the second handles the error/edge case, and the third gives a downstream routing hint. No filler or redundant restatement of the title or schema exists.

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 read-only tool with an output schema, the description covers what is returned, the key error case, and a relevant downstream usage. The annotations already cover safety and idempotency, and the schema covers parameters, so nothing an agent needs to call this tool 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 description coverage is 100%, so both agent_id and session_token are already fully documented in the input schema. The description adds no new parameter-level semantics beyond referring to 'agent' generically, which is acceptable but not a value-add beyond 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 uses the specific verb 'Read' and names the exact resource: the linked organization (name, slug, country, default address) and members (user_id, name, role, email) for an agent. This clearly distinguishes it from sibling tools like agent_create, agent_update, and agent_notify, whose names imply different purposes.

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 gives clear context for when to use this tool: to read an agent's linked organization and members. It also handles the unset organization_id case by instructing the agent to return org_not_linked and explicitly not to invent join_org, and points to members as the target for agent_notify. It stops short of explicitly comparing against alternatives as a primary selection guide, so a slight deduction applies.

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