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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. What the description adds beyond that is genuinely valuable: the return value is procedural instructions (screens, buttons, fields) and the tool performs no action on its own, plus the note that ServiceTrade offers no official MCP server, which explains why a browser fallback exists.

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 most important fact — that this returns instructions, not deficiencies — arrives only in the second sentence, after a generic 'from ChatGPT, Claude or any AI agent' clause that adds nothing. The closing sentence about ServiceTrade's REST API and OAuth2 is tangential and only loosely justified as explaining the browser fallback.

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 zero-parameter, non-destructive tool with no output schema, an agent mainly needs to know what comes back and what to do next, and the description supplies both (step-by-step instructions, then cotlet_browser_* execution). Only the return format (markdown vs structured) is left unstated, which is a minor gap.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly implies no filtering arguments are needed.

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 second sentence clarifies the actual function — returning a step-by-step how-to for listing deficiencies rather than the deficiency data itself — but the opening sentence ('List deficiencies in the user's own ServiceTrade account') sets up the opposite expectation, creating real ambiguity about what an agent will receive. It also never distinguishes this from sibling ServiceTrade tools such as servicetrade_list_jobs, which a reader could reasonably expect to behave differently.

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?

The description does sequence the workflow: get the steps here, then execute them with cotlet_browser_* tools in the ServiceTrade Cloud Browser, and it states the tool 'opens nothing by itself.' That is implied-but-useful guidance, yet there are no explicit exclusions or comparisons telling the agent when a different ServiceTrade tool would be the better pick.

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