Show Next Available Number For Observation Items

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

The description claims the tool returns a paginated JSON array of Observations, which directly contradicts the tool's name and likely actual behavior (returning a single number). This misstatement is critical and not mitigated by annotations, which already indicate readOnlyHint and idempotentHint.

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?

The description is concise but structurally flawed due to contradictory statements. The first sentence is clear, but the following sentences introduce confusion. Every sentence should contribute coherently.

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 the absence of an output schema, the description must clarify the return value. It initially says 'next available number' but then contradicts with 'paginated array of Observations,' leaving the actual response format unclear. This is a significant gap for a simple tool.

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 already covers all three parameters with descriptions (100% coverage). The description merely restates that project_id is required and that page/per_page control pagination, adding minimal extra meaning. Baseline 3 is appropriate.

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 initially states 'Returns the next available number for an observation item,' which is clear, but then contradicts itself by saying 'Use this to fetch the full details of a specific Observations by its identifier' and 'Returns a paginated JSON array of Observations.' This inconsistency severely undermines the purpose clarity.

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 mentions 'current Project' and required 'project_id' but provides no guidance on when to use this tool versus alternatives like 'get_next_available_number' or 'get_next_available_number_by_spec_section.' There is no differentiation or exclusion criteria.

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