FreeDailyPro Business Documents

business_poa_draft

Read-onlyIdempotent

Power of attorney draft

Input Schema

Name	Required	Description
`agent`	Yes
`limits`	No	What the agent may not do.
`powers`	Yes	What the agent may handle, for example "banking, paying bills and filing taxes".
`durable`	No	Continues if the principal becomes incapacitated. Default true.
`effective`	No
`principal`	Yes
`governingLaw`	No	Whose law governs, for example "the State of Texas" or "England and Wales". Default: the place where the property or the parties are.
`successorAgent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 3, 2026

addedInput schema / properties / durable

Added value: +{
+  "description": "Continues if the principal becomes incapacitated. Default true.",
+  "type": "boolean"
+}

addedInput schema / properties / effective

Added value: +{
+  "enum": [
+    "immediately",
+    "upon-incapacity"
+  ],
+  "type": "string"
+}

addedInput schema / properties / governingLaw

Added value: +{
+  "description": "Whose law governs, for example \"the State of Texas\" or \"England and Wales\". Default: the place where the property or the parties are.",
+  "maxLength": 120,
+  "type": "string"
+}

addedInput schema / properties / limits

Added value: +{
+  "description": "What the agent may not do.",
+  "type": "string"
+}

addedInput schema / properties / powers / description

Added value: +"What the agent may handle, for example \"banking, paying bills and filing taxes\"."

addedInput schema / properties / successorAgent
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedNov 1, 2026
- addedInput schema / properties / agent / minLength
```
Added value: +1
```
- addedInput schema / properties / powers / minLength
```
Added value: +1
```
- addedInput schema / properties / principal / minLength
```
Added value: +1
```
First observedOct 24, 2026

TDQS

D1.7/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds nothing beyond that: no statement of what the tool emits (plain text, PDF, filled template), no legal/compliance caveats, no note on whether the draft is jurisdiction-aware. No contradiction with annotations, but zero added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only four words, so there is nothing to trim, but that brevity is under-specification rather than concision. There is no structure, no front-loaded statement of action, and no sentence that meaningfully earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An 8-parameter legal-document generator with no output schema needs the description to explain what is produced and under what conditions. A four-word fragment leaves the agent unable to predict the result or judge suitability for a legal use case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, and four parameters (agent, principal, effective, successorAgent) have no description anywhere. The description supplies no meaning for any parameter, not even the required principal/agent/powers triad, so it fails to compensate for the coverage gap on an 8-parameter legal document tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Power of attorney draft" merely restates the tool name (business_poa_draft) and title (Business Poa Draft). It never says what the tool actually does — generate, fill, or template a legal document — nor how it differs from siblings like business_lease_draft or business_nda_draft beyond the resource noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool or the conditions under which a business POA draft is the right output. The sibling list contains many other document-drafting tools, and nothing here helps route between them.

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

All FreeDailyPro Business Documents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?