Check If Number And Revision Entered Are Available Or Duplicated.

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

Annotations indicate a safe read, but the description contradicts itself: first describing a check returning availability/next_number, then describing a paginated list of Submittals. This inconsistency obscures actual behavior.

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 moderately concise but includes extraneous and contradictory information about returning Submittals, reducing efficiency.

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?

Without an output schema, the description should clarify the return format. It instead provides conflicting information (availability check vs. list of submittals), leaving the tool's actual response ambiguous.

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 standard. The description adds minor context about pagination control but does not significantly enhance understanding beyond the schema.

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 the tool returns availability/duplication status, which matches the name. However, it also claims it returns a paginated JSON array of Submittals, creating confusion about the tool's actual purpose.

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 versus siblings like list_submittals or get_next_available_number. The misleading statement 'Use this to read information about Submittals' undermines clarity.

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