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

With no annotations, the description carries disclosure duties. It surfaces important behavioral details: the 'unknown' status definition ('no expiry date on record, not lapsed') and the 25k row cap with the instruction to check the truncated flag and narrow filters. This is substantial, though it doesn't address authorization, rate limits, or exact output 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?

Three tight sentences, each earning its place: output definition, use case, and a concrete limit warning. The core verb and purpose are front-loaded, with 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 tool with no output schema or annotations, the description conveys the result dimensions (counts, regions, laws, status split) and the truncation behavior. It could be more explicit about the exact return fields, but the essentials for calling it correctly are present.

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 has 100% description coverage, with each parameter already bounded and described. The description adds only a generic hint to 'narrow filters,' which doesn't enrich any specific parameter 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?

The description opens with a concrete verb and target: 'Rank developers by LTS count,' and specifies the output components (regional footprint, law breakdown, status split). It does not explicitly contrast with sibling tools like lts_by_region or lts_by_city, so it misses the top score for sibling differentiation.

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 states clear intended use cases: 'developer intelligence, competitive analysis, and identifying which developers dominate specific regions or housing segments.' It lacks explicit when-not-to-use or alternative tool guidance, so it stays a 4 rather than 5.

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