segments_by_tag

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

Annotations already indicate a safe read-only, idempotent operation. The description adds that tag matching is exact and that limit is a 1-100 range with a default of 20, which are useful behavioral details beyond the schema.

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 extremely compact, leading with a one-sentence purpose and followed by a minimal Args list. No extraneous information.

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 only 2 parameters and the presence of an output schema, the description covers the purpose, parameter semantics, and prerequisite workflow. It lacks explicit guidance on when to use alternatives, but is otherwise sufficient for a simple filtered read tool.

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 has no property descriptions (0% coverage). The description explains that tag must be an exact value from list_tags and clarifies limit's range/default. However, the stated default of 20 conflicts with the schema's default of null, which could confuse an agent.

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 states 'List segments carrying a given tag name,' which clearly identifies the verb (List), resource (segments), and scope (by tag). It differentiates from sibling tools like list_segments (unfiltered) and list_tags (tags only).

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?

It instructs that the tag must be an exact name as returned by list_tags, establishing a clear prerequisite and workflow. It also specifies the limit range, but does not explicitly contrast with list_segments or provide exclusion criteria.

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