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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no indication of what the certificate contains, its format, size, or any permission requirements.

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 description is short but wasted: the identical endpoint sentence appears twice, and the only substantive content is a boilerplate reference to describe_operation. It is under-specified rather than concise.

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 and zero schema description coverage, the description needs to explain what is returned (e.g., certificate file, metadata) and how 'id' maps to a signature. It supplies none of this, leaving an agent unable to predict the response.

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%, so the schema provides only raw types with no meaning. The description adds nothing about the 'id' parameter beyond the implicit path placeholder, and gives no guidance on the undocumented 'query' object.

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 restates the tool name/title as a raw URL path ('GET /api/signatures/:id/certificate') without explaining what a signature certificate is or what fetching it yields. It gives no differentiation from siblings such as get_signatures_by_requestId_events 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?

There is no statement of when to use this tool versus alternatives. The only guidance is a pointer to describe_operation for native request schemas, which explains where to look for more detail rather than when this endpoint applies.

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