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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it returns classes and documents, which is useful context. However, it does not disclose potential errors, required authentication, or any other behavioral traits beyond the basic read operation. With annotations covering the main safety aspects, a 3 is appropriate.

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?

A single sentence with zero waste, front-loading the core action and outcome. It is appropriately sized for a simple read operation and contains no redundant information.

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 straightforward get-by-ID operation with an output schema present, the description is sufficiently complete. It states what the tool returns (one application with classes and documents) and the annotations cover the read-only nature. No critical information an agent needs to invoke it correctly is missing, though it could mention that a valid applicationId is required, but the schema already enforces that.

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%: the parameter applicationId is fully described as a UUID value wrapper. The description does not add any additional meaning or format details beyond what the schema provides. Since the schema already documents the parameter, the baseline of 3 applies.

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 states a clear verb ('returns') and resource ('one application') and specifies what is included ('its classes and documents'). This distinguishes it from sibling tools like trademark_get_list_applications, which retrieves multiple applications, and trademark_start_application, which creates a new one. The purpose is unambiguous.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it, nor does it reference sibling tools or conditions for selection. The intent is implied (when you need a single application's details), but there is no explicit routing instruction.

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