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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered by structured data. The description's added value is the enumeration of returned content, which is useful but omits auth requirements, rate limits, or error behavior (e.g. what happens on an unknown slug).

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 sentence, front-loaded with the verb and scope, and every listed noun corresponds to actual returned content. No filler.

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 read-only single-parameter lookup, the annotations carry the safety profile and the description explains the payload, so basic invocation is covered. The gap is boundary-setting against three closely related siblings, which matters for correct tool selection here.

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 the single slug parameter is documented with an example ('stripe'). The description adds nothing beyond the schema, so the baseline 3 for a fully documented single-parameter schema 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+resource ('Get one logo's details') and enumerates the content returned (variants, brand color, SVG URLs, React component name, shadcn command). However, it never distinguishes this aggregate call from siblings get_logo_svg and get_logo_component, which appear to return overlapping subsets.

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?

No when-to-use guidance, no mention of alternatives, and no conditions that would route an agent to get_logo_svg, get_logo_component, or search_logos instead. The overlap with those siblings is left entirely to inference.

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