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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds that it returns brand IDs, names, handles, and display settings, but this is likely already in the output schema. No additional behavioral traits (e.g., ordering, filtering, rate limits) are disclosed, so the description adds only marginal value beyond 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 concise with two sentences. The first sentence front-loads the purpose and return fields, and the second sentence provides a useful pointer to a related tool (postnitro_set_defaults). It is efficient and without fluff, though the second sentence is not strictly necessary for calling the tool correctly.

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?

Given the tool's simplicity (2 optional parameters, no required params, output schema present, and annotations covering read-only/idempotent/non-destructive behavior), the description is complete. It states the tool's purpose, the return fields, and a relevant next step. Nothing an agent needs to invoke it correctly is missing.

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?

Both parameters (page and limit) have complete descriptions in the input schema (100% coverage), including defaults and maximums. The tool description adds no extra semantics about how these parameters affect the results beyond what the schema already states. This matches the baseline of 3 when schema does the heavy lifting.

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 clearly states a specific verb ('List') and a specific resource ('available brand configurations'), and specifies the returned fields (brand IDs, names, handles, display settings). This distinguishes it from singular retrieval tools like postnitro_get_brand and creation tools like postnitro_create_brand without needing to inspect the schema.

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 not explicitly compare this tool to alternatives or state when not to use it. It only implies usage for listing available brands, and the mention of postnitro_set_defaults suggests a follow-up action but not a selection criterion. The usage context is implied by the tool's nature as a list operation, but no explicit exclusions or alternatives are given.

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