ghl_invoice_schedule_create

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

Annotations indicate readOnlyHint=false (write) and destructiveHint=false, so the description does not need to restate those. However, it adds the endpoint and OAuth scopes but does not disclose any behavioral traits such as creating a recurring invoice schedule, what happens upon creation, or any side effects. With annotations present, this is adequate but minimal.

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 (4 lines) and front-loaded with the title and a clear verb-resource phrase. It includes endpoint and OAuth scopes without unnecessary words. However, it could be slightly more informative without being verbose, so 4.

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 complexity of the input schema (many nested required fields), the description is too minimal. It does not explain what an invoice schedule is, how it relates to invoices, or what the return value looks like (no output schema). The sibling list hints at related tools but the description does not leverage that context. An agent would struggle to understand when to use this tool effectively.

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 schema has 100% description coverage for its nested properties, so it already provides rich parameter semantics. The description adds no further parameter information. Baseline score of 3 is appropriate; no extra value from description.

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 'Create Invoice Schedule' and 'API to create an invoice Schedule', which identifies the verb (create) and resource (invoice schedule). While it distinguishes from siblings by being the create operation among invoice schedule tools (activate, cancel, delete, etc.), it does not explicitly differentiate beyond the tool name, so a slight deduction.

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 versus alternatives (e.g., when to create a schedule vs. update or activate). No prerequisites or exclusions mentioned. The description only states the endpoint and OAuth scopes, leaving the agent without usage context.

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