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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of what events are returned, ordering, pagination, or empty-result 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?

The single meaningful sentence is duplicated verbatim, and the remaining content is an internal operation ID that serves no selection purpose. There is no front-loaded statement of intent.

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, no parameter documentation, and a nested free-form query object, the description should explain what this returns (a list of signature events) and how to filter it. It does neither.

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 two parameters (requestId path param and an untyped free-form query object). The description does not explain requestId semantics or what query filters are accepted, so it fails to compensate for the schema gap.

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 and title verbatim ('GET /api/signatures/:requestId/events') twice, plus an opaque operation ID. It technically implies reading signature events for a request, but adds nothing to distinguish it from siblings like get_signatures or get_signature_management.

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, when-not-to-use, or alternative guidance at all. The only pointer is that describe_operation 'provides native request schemas', which is a schema-retrieval hint, not usage guidance, and the massive sibling list makes routing ambiguous without help.

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