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

Annotations already establish that the operation is read-only, idempotent, and non-destructive, so the description's safety burden is low. It adds some value by listing the profile fields returned, but does not disclose behaviors such as response shape or error conditions beyond what annotations already convey.

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 a single, well-structured sentence that front-loads the core purpose and then lists the specific fields in a readable, comma-separated sequence. Every word adds useful information with no redundancy.

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 single-parameter read-only getter with no output schema, the description compensates by enumerating the key fields the profile contains. It is nearly complete, though it could slightly improve by clarifying how the response relates to brand_list or what a missing brand slug would yield.

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 coverage is 100% and the only parameter is documented as 'Brand slug', so the description adds little beyond the schema. The phrase 'for one brand' reinforces that the parameter identifies a single brand, but no format or usage details are added.

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-resource phrasing, 'Full profile for one brand', and enumerates exactly which profile components are included. It clearly distinguishes brand_get from brand_list by emphasizing 'one brand' vs. a broader list.

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 implies the tool is used when you need a complete profile for a single brand, but it does not explicitly state when to avoid it or name alternatives like brand_list or brand_activate. Usage context is present but left to inference.

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