get_igp24_label_progress

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

Given no annotations, the description discloses key behaviors: aggregate bulk endpoint, pagination limits (100 default, 5000 max), filter repeatability, cursor invalidation, and published state. Could include more on error handling or rate limits, but sufficient for safe usage.

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?

Efficiently structured with a clear opening sentence followed by bullet-like details. Each sentence adds value, but could be slightly more concise by grouping related info. Still, no wasted words.

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?

Provides good context on pagination, filtering, and published state, but lacks full explanation of return values beyond data.labels[] and meta.published. Without an output schema, more detail on response fields would improve completeness.

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?

With 0% schema description coverage, the description adds meaning for 4 of 5 parameters (label, labels, limit, cursor). Explains label vs labels alternatives and limit defaults. Missing explanation for 'include_empty' parameter, leaving it ambiguous.

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?

Clearly states 'Get aggregate IGP24 participant progress by transitive group label' with added scope and response structure details. Distinguishes from sibling list endpoints by explaining it returns data.labels[] rather than data.items[].

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?

Provides explicit usage guidance: limits default and max, filter alternatives (label vs labels), cursor invalidation on filter change, and behavior before publication. Lacks explicit alternative tool names but context is clear.

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