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

readOnlyHint=true already tells the agent this is a safe read, and the description adds nothing beyond that: no pagination behavior, no statement about whether inactive/archived branches are included, no auth context. For a list endpoint on a multi-tenant organization resource, those are the details that actually matter.

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?

A single short sentence with the scope front-loaded and no filler. It is not padded, though it is also so terse that it borders on under-specification rather than earning a 5.

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 one-parameter read tool with readOnlyHint and no output schema, the minimum is covered, but return-shape expectations and pagination are unstated and there is no cross-reference to the create/update/delete location siblings an agent will need alongside it.

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?

The single required parameter organizationId has 0% schema description coverage, so the description should compensate; it only weakly implies org scoping via 'an organization's'. The parameter's meaning is largely self-evident from its name and type, but its format (ID type, where to obtain it) is undocumented anywhere.

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 (List) and resource (organization's locations/branches), so the operation is unambiguous. However, it does nothing to distinguish itself from the sibling location tools (create_/update_/delete_organization_location) or from other list_organization_* tools; an agent still has to infer the contrast from names.

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?

No when-to-use guidance, no prerequisites (e.g. required permissions or organization membership), and no mention of alternatives such as update_organization_location or get_organization_hierarchy. Usage is only implied by the verb 'List'.

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