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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds a non-obvious payload trait — that the description and suggestions fields are omitted from results — which the annotations do not convey. It stops short of covering pagination or result limits.

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 short sentences, front-loaded with the core action before the exclusions and the parameter constraint. The final sentence largely restates the schema's mutual-exclusivity note, a minor redundancy, but overall there is little wasted text.

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?

With no output schema, the description partially compensates by describing what the result set excludes. It omits the state parameter's filtering behavior and any pagination/volume expectations, but for a simple read-only list tool with 100% schema coverage the gaps are small.

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 both logId and organizationId already carry descriptions including their mutual exclusivity, which the description merely restates. The description does not mention the state filter or its default of 'Open', so it adds no meaning beyond the schema. Baseline 3 applies.

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 ('Get a list of recommendations') and scopes it to 'a log or an organization'. It explicitly differentiates itself from the sibling recommendations_get_details, which is the closest competing tool, so an agent can choose 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?

It names the alternative tool and the exact condition that selects it ('Does not include the description and suggestions fields; call recommendations_get_details for those'), plus a hard invocation constraint ('Specify exactly one of logId or organizationId'). Nothing about routing is left to inference.

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