heddle_entity_churn_count_get

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

Given no annotations, the description adds value by clarifying return value for unseen entities (0 not error). However, it lacks disclosure on idempotency, permissions, or side effects.

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 and a key behavioral trait. 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?

Despite having an output schema, the description is too minimal for a complex tool with 7 parameters, nested objects, and many siblings. Missing guidance on sorting, pagination, and how entity_refs is constructed.

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 7 parameters with 0% description coverage. The description only mentions 'optional window' without explaining any parameter structure or constraints, leaving the agent with no additional meaning beyond schema fields.

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 clearly states it is a per-entity change-event count with an optional window. It specifies a behavior for never-observed entities, but does not differentiate from sibling tools like 'churn' or 'heddle_change_list'.

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 context on prerequisites or limitations beyond the brief behavior note.

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