Get Next Available Number By Spec Section

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

Annotations indicate readOnlyHint=true, but the description does not mention the conditional behavior (only works if numbers submittals by spec section is enabled) or what happens when the condition is false. It claims to return a JSON object but does not detail the structure or potential errors.

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 verbose and includes extraneous details like Procore API version and endpoint. It is not front-loaded with the core purpose, and the contradictory statements make it harder to parse quickly.

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 complexity (conditional behavior, return of two items), the description fails to explain the return structure or handle edge cases. No output schema, so the description should clarify but instead confuses by mentioning 'full details of a specific Submittal.'

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% and parameters are documented in the schema. The description adds a line listing required parameters, but this adds no value beyond the schema. Baseline score of 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 states it 'returns the next available number and next spec section number' but then says 'use this to fetch the full details of a specific Submittals by its identifier,' which contradicts the tool name and primary purpose. This muddles the 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?

No explicit guidance on when to use this tool vs alternatives. The description mentions a conditional 'if numbers submittals by spec section is enabled' but does not explain how to decide between this and other submittal-related tools.

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