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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description's 'List' verb is consistent with that, and it adds semantic context about what technologies are used for, but no extra behavioral details such as pagination behavior or return shape.

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?

A single, front-loaded sentence that names the action and resource immediately, adds clarifying context, and includes useful examples without any filler or repetition.

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 simple read-only list tool, the description, schema, and annotations together cover what the tool lists, its domain, and pagination controls. The lack of an output schema is not a significant gap since the listed items are straightforward tech-stack tags, though a note on how this differs from tag_list would have been slightly more complete.

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?

The input schema covers 100% of the parameters, with page and page_size fully described including defaults, minimums, and maximums. The description adds no parameter-level information, so it neither improves nor harms parameter understanding beyond the schema.

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 and resource ('List technologies'), defines the resource as 'tech-stack tags', and gives concrete examples ('React', 'PostgreSQL'). The phrase 'that projects and teams can be labelled with' clarifies the domain and distinguishes this from generic tagging tools like tag_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 when to use the tool: when a list of tech-stack tags suitable for labelling projects and teams is needed. However, it provides no explicit when-not-to-use guidance or alternatives (e.g., tag_list for non-tech tags), leaving the choice mostly to inference.

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