Get Next Available Number

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

While annotations indicate read-only and idempotent behavior, the description adds confusion by describing paginated submittal array return, which doesn't align with the stated purpose of getting a next available number.

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 of moderate length but contains redundant and contradictory information, making it less effective than a concise, focused statement would be.

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 lack of output schema and the complexity of the tool (pagination, project context), the description fails to provide coherent and complete guidance, mixing two distinct operations.

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 100%, so baseline is 3, but the description does not clarify how parameters relate to the next available number; instead it introduces submittal concepts, reducing clarity.

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 states 'Returns the next available number' but then diverges to 'fetch the full details of a specific Submittals' and 'Returns a paginated JSON array of Submittals'. This inconsistency makes the tool's purpose unclear and contradictory.

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?

Mentions an alternative tool (Get Next Available Number By Spec Section) but then incorrectly instructs to use this tool for fetching submittal details, confusing when to use this tool versus the alternative.

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