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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description contributes nothing beyond that - no note on result scope, pagination, or what "outfits" means here - so it fails to add the extra context expected when annotations carry the baseline.

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?

One short, front-loaded sentence with no filler, which is structurally fine. However, the brevity comes from omission rather than economy - the sentence is under-specified for a tool with a scoping parameter.

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?

This is a simple read-only list operation with full annotation coverage, 100% schema coverage on its one optional parameter, and no output schema, so the burden on the description is low. Still, it never clarifies whether the context parameter changes results or what the listing contains, leaving the agent with a minimally viable definition.

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 there is a single optional 'context' parameter whose schema description already spells out "personal" (default) or "team:<id>". The description adds nothing about this parameter, so the baseline 3 for schema-covered parameters 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 is essentially the title restated: the tool is named outfit_list, titled "List Outfits", and described as "List your outfits." It states a verb and resource but adds no information an agent did not already have from the name/title, and gives no scope (personal vs team) or differentiation from the many other *_list siblings.

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 when-to-use guidance, no mention of alternatives (scene_list, persona_list, product_list, connector_list, etc.), and no conditions under which this tool should be preferred or avoided. The agent must infer everything from the name.

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