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

No annotations provided, so description carries full burden. It discloses that company counts are computed live, that subsegment ids in company data may not be in the taxonomy snapshot (flagged in_taxonomy: false). This is good transparency, though it doesn't mention pagination or side effects (which are minimal for a read-only list).

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?

Two sentences, first sentence front-loads the main action and output, second adds usage guidance and behavioral note. Every sentence adds value; no fluff.

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?

Despite no output schema, the description explains return fields (live company count, parent segment id/name) and the optional filter. It also mentions the in_taxonomy flag. This is sufficient for a list tool with simple parameters.

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%, baseline 3. Description adds an example value ('materials') and clarifies that omitting the parameter returns all 12 segments, providing helpful context beyond the schema description.

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?

Description clearly states it lists every subsegment with live company count and parent info, optionally filtered by segment. It distinguishes from sibling get_segments by explicitly mentioning both as ways to discover subsegment values. Verb+resource+scope are specific.

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?

Explicitly advises using this tool (or get_segments) before calling get_subsegment or filter_companies, providing a clear usage context. Mentions optional filtering and links to an alternative tool.

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