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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safe-read profile is fully covered by structured data. The description adds the selector constraint (one of logId/organizationId), which is useful, but discloses nothing about return shape or error behavior.

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 short sentences, front-loaded with the purpose before the parameter constraint. Nothing is wasted and no filler remains.

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?

Low complexity, one required parameter, full schema coverage, and annotations carrying the safety profile mean the agent has nearly everything needed. The only missing element is what 'details' actually returns, which is unstated and there is no output schema to fall back on.

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 scope parameters and recommendationId are already documented with their mutual exclusivity. The description restates that same exclusivity without adding format or behavioral detail beyond the schema, which is the expected baseline.

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 ('Get details') and resource ('a single recommendation'), with scope narrowed to a log or organization. This clearly separates it from recommendations_list, though it does not explicitly name that sibling as an alternative.

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 instruction to specify exactly one of logId or organizationId is a genuine usage constraint, but it is a duplicate of the schema's own 'mutually exclusive' notes rather than guidance about when to reach for this tool instead of recommendations_list or logs_get_details. Usage is implied by the get/details naming convention.

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