legal_partnership_agreement_packet

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds almost no behavioral context beyond JWT/tenant/company scoping. It does not disclose what the action produces, modifies, sends, or persists, so an agent cannot anticipate side effects.

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 short, front-loaded, and uses a clear Args list without unnecessary fluff. It is structurally efficient, though the brevity comes at the cost of domain-specific substance.

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?

For a legal domain action with two completely undocumented parameters and many sibling legal tools, the description is not complete enough. An agent cannot determine what objective to put in message, what JSON to pass in inputs, or what result to expect, despite the existence of an output schema.

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?

With 0% schema description coverage, the description must compensate, but it only labels message as 'free-text objective' and inputs as 'optional JSON string of structured inputs.' These are generic placeholders and do not explain what content the partnership agreement packet needs, how the two parameters interact, or what structured inputs would be expected.

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 action: run the legal domain agent action `partnership_agreement_packet`, and explains it routes through the domain-agent dispatcher. The resource is specific, but it does not describe what a partnership agreement packet actually is or how it differs from sibling packet tools like legal_sales_agreement_packet or legal_nda_packet.

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 is given on when to use this tool versus alternatives such as legal_partnership_onboarding_loop, legal_contract_review, or the other legal packet tools. The description explains routing mechanics but provides no selection criteria, prerequisites, or exclusions.

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