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

Annotations already convey that this is read-only and non-destructive, so the safety profile is covered. The description adds company scoping, which helps interpret filter.companyId, but discloses nothing about defaults, filtering behavior, or pagination. There is no contradiction with annotations.

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 a single sentence with no filler, and the scoping fact is front-loaded. It is concise, though the brevity leaves substantive gaps; there are no structural problems.

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?

An output schema exists and annotations cover safety, so return values and read-only behavior need not be repeated. However, the description omits optional filtering and pagination behavior and gives no guidance on how this tool relates to sibling applications like trademark_get_application, making it minimal but not complete.

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 description must compensate for undocumented parameters. It only clarifies the companyId concept via 'a company's applications'; pageSize, pageToken, and filter.statuses remain unexplained. This is insufficient compensation for three otherwise undocumented parameters.

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 uses a specific verb and resource: 'lists a company's applications.' It clearly indicates this is a plural/list operation rather than a single-record get. It does not explicitly contrast with trademark_get_application, so sibling differentiation is left mostly to the tool name.

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 guidance on when to use this tool versus alternatives, no mention of optional filters like statuses, and no indication of whether companyId is expected. An agent must infer usage from the name and schema rather than from the description.

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