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 'GET' in the description adds nothing beyond structured data. The description does not state what is returned, whether results are paginated, or what auth/scope is needed; the only extra information is the describe_operation pointer.

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?

It is short, but the same sentence is duplicated verbatim, which is pure waste. The only substantive content (operation ID and the describe_operation hint) is buried after the repetition.

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, a fully undocumented free-form query parameter, and no explanation of what the endpoint reads or returns, an agent is left guessing. The describe_operation hint is the sole mitigating element; everything else an agent would need must be discovered elsewhere.

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%, and both parameters are opaque: a free-form 'query' object with arbitrary keys and an empty 'params' object with additionalProperties=false. The description offers no parameter names, formats, or examples, only the generic note that describe_operation holds native schemas — a pointer, not parameter semantics.

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 is the endpoint path repeated twice: 'GET /api/signature-management.' It restates the name/title rather than stating what the operation returns or accomplishes, so an agent cannot distinguish it from a dozen other signature-related GETs in the sibling list on the basis of the description alone.

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 when-to-use, when-not-to-use, or alternative named. The only actionable hint is 'describe_operation provides native request schemas', which points at a discovery mechanism rather than at selection criteria among siblings like get_signatures or get_signatures_by_requestId_events.

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