churn

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

Discloses that never-observed entities return 0, not an error, which is valuable. But it does not mention mutability, auth needs, rate limits, or specifics about the window parameter. Since annotations are absent, the description carries full burden and is only partially adequate.

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 concise sentences front-loaded with purpose. No wasted words, but could be expanded with important details without losing conciseness.

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 7 parameters including a nested object, cursor, and sort fields, the description is insufficient. It fails to explain what 'SEIs' means, how the window parameter is structured, sort options, or pagination behavior.

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 no parameter-specific information beyond the general purpose. It mentions 'window' but does not explain its structure or the other 5 parameters.

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 it counts change events per entity over an optional window and handles never-observed entities. However, it does not differentiate from similar siblings like 'changed' or 'heddle_entity_churn_count_get'.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, exclusions, or preferred scenarios.

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