Neurons Claims

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

Annotations already declare that this mutates state (readOnlyHint=false) but is not destructive and is closed-world. The description adds meaningful context with 'advisory', signaling the locks are cooperative rather than enforced. It does not disclose lock expiry/TTL behavior, conflict handling, or the effect of the force flag, which are the behaviors an agent most needs.

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 short, front-loaded sentences with no filler; the purpose comes first and the action enumeration second. It is efficient, though the action list is a bit telegraphic.

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 six-parameter mutation tool with no output schema and no annotation detail on conflicts or expiry, the description is thin. It says nothing about lock duration, what a failed claim returns, what force overrides, or what list returns, leaving significant gaps an agent would need to call it correctly.

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 0%, so the description carries the full burden, yet it only mentions paths and the 'all' shorthand for release. Four of six parameters (repo, force, reason, ttl_minutes) are never explained, so the agent must guess at force semantics and TTL defaults from the name alone.

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 first sentence names a specific mechanism (advisory edit locks) and the concrete problem it solves (two sessions editing the same files). The second sentence enumerates the three actions, so the agent knows this is a lock-management tool. It does not need sibling differentiation since the siblings are unrelated collaboration tools.

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 rationale sentence implies when to use it (before editing shared files), and the action list hints at the lifecycle. However, there is no explicit when-to-use/when-not guidance, no mention of what happens on a conflicting claim, and no statement of which action applies in which situation beyond the parenthetical hints.

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