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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description goes beyond them by enumerating what the decision record contains (decision type, issue date, outcome values, issues/rules, document title + download link) and naming the upstream source (USPTO ODP), which is genuinely useful context absent from the 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?

Front-loads verb and resource, then the payload and provenance in two tight sentences. The trailing 'Powered by the USPTO Open Data Portal' clause is the only mildly expendable element, but it earns its place as provenance for a data-lookup tool.

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, the description must carry the return-value burden, and it does — outcome enumerations and document link are spelled out. Parameters and safety are fully covered by schema and annotations, so only a minor gap (no mention of error behavior for an unknown appeal number) remains.

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% and all three parameters are documented in the schema, including the include_raw semantics and the _apiKey. The description only repeats the appeal-number example format, adding no meaning beyond the schema — the baseline 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?

States a specific verb and resource: 'Get one USPTO ex parte Appeal decision by its appeal number.' The singular 'one ... decision' plus the appeal-number keying distinguishes it cleanly from siblings like ptab_search_appeals and ptab_recent_decisions without needing their schemas.

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?

Usage is implied by 'by its appeal number' — an agent infers it needs a known appeal number and should search first otherwise — but the description never names ptab_search_appeals as the way to obtain one, nor states any when-not condition. Adequate implied guidance, no explicit routing.

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