create_a_deal_role

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

Annotations already declare non-idempotent (idempotentHint: false) and readOnlyHint: false. The description adds 'Not idempotent — calling twice may create duplicates,' which aligns with annotations but does not provide new behavioral insights beyond what is already structured. With annotations, the description adds minimal extra value.

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, front-loaded with a symbolic summary, endpoint, and clear purpose. Every sentence contributes: it states the action, the resource, the HTTP method, and a key behavioral note. No wasted words.

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 simplicity of the tool (one parameter, no output schema), the description is nearly complete. It covers the non-idempotent behavior, which is critical. It does not explain what a deal role is, but that is domain knowledge. With annotations providing safety traits, the description is sufficient.

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 has 100% description coverage for its single parameter (body with title described as 'Title for the new deal role'). The description does not add additional meaning or constraints beyond the schema, so 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 clearly states the tool creates a deal role, with the action 'Create a deal role' and the resource 'Deal Roles'. It also includes the HTTP method and endpoint, making the purpose precise. The tool name itself is unambiguous, distinguishing it from siblings like 'create_a_deal_new' which creates a deal.

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 guidance on when to use this tool over alternatives. While it mentions non-idempotency, it does not specify prerequisites, filters, or context. Among many sibling create tools, there is no differentiation provided.

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