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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful scope details: only metadata is returned, no image bytes, and guest history is excluded. However, it says nothing about pagination behavior, ordering, or default limits beyond what the schema provides.

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?

Two tight sentences with no filler. The scope statement is front-loaded and the exclusion follows immediately, making the description easy to parse.

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?

The output schema and annotations reduce what the description must cover, and the scope/exclusion sentences are useful. Still, for a three-parameter list tool with 0% schema description coverage, the description leaves pagination and the kind enum's 'all' behavior unaddressed.

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 all three parameters. It partially maps to the kind enum by listing 'photos, products, looks and DressMe requests,' but it does not mention the 'all' value, limit, offset, or pagination semantics.

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: 'Read metadata for your saved personal photos, products, looks and DressMe requests.' This clearly identifies the tool as a metadata listing endpoint, though it does not explicitly differentiate itself from siblings like get_trifit_account or search.

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 explicit guidance on when to use this tool versus alternatives such as get_trifit_try_on, search, or fetch. The exclusion 'No guest history transfer' hints at a boundary but does not name alternatives or state when this tool is preferred.

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