Create Specification Set

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true) already cover safety. Description adds return behavior (HTTP 201) and required params, but no new behavioral context. No contradiction.

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?

Three sentences conveying purpose, usage, and endpoint. Could omit 'Procore API: ...' line for tighter structure, but overall concise and front-loaded.

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?

Covers purpose, required params, and return behavior. Lacks explanation of optional 'date' parameter and potential constraints (e.g., uniqueness of name). Adequate for a simple create tool but leaves gaps.

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 description adds little beyond listing required parameters (project_id, name) already marked required in schema. Does not elaborate on optional date parameter. Baseline 3 maintained.

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?

Description states 'Create a new Specification Set in the specified project' with a clear verb and resource. The name and description distinguish it from siblings like create_specification_area or create_specification_section. Minor inconsistency: says 'create a new Specifications' but overall clear.

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?

Implies usage via 'Use this to create a new Specifications in Procore' but does not explicitly state when to use this tool versus alternatives like create_specification_section. No exclusions or when-not-to-use guidance.

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