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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond pointing at describe_operation for schemas — no pagination, filtering, or return-shape context. No contradiction with annotations, but very little added value.

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 same sentence is printed twice verbatim, which is pure waste in an already minimal description. The remaining content is front-loaded but contains almost no information, so brevity here reflects under-specification rather than tight writing.

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 zero-required-parameter, nested-object tool with no output schema and 0% parameter documentation, an agent cannot tell what a 'share log' returns or what to pass in the opaque query/params objects. The describe_operation pointer is the only lifeline, and it is not enough to call this tool correctly on first attempt.

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 0% for the two top-level parameters (query, params), and 'params' is an empty closed object with additionalProperties:false, which is genuinely confusing. The description's only compensation is deferring to describe_operation; it gives no meaning for query vs params, no expected fields, no examples.

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 only restates the endpoint path 'GET /api/recon-docs/share-log', which is already encoded in the tool name and title. It names a resource (share log for recon docs) but no verb-level intent, no statement of what the log contains, and no differentiation from the many other recon-docs siblings (audit-packages, statements, templates). This is close to tautology.

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?

There is no statement of when to call this versus alternatives such as execute_read or the other get_recon_docs_* tools. The single actionable hint is 'describe_operation provides native request schemas', which weakly implies a prerequisite step but says nothing about selection or exclusions.

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