invoices_get_invoice_schedule

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no further behavioral context—no mention of what the schedule contains, whether it returns the full schedule, or any edge cases. It merely restates the action without enriching the agent's understanding.

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 extremely short, but this is under-specification rather than effective conciseness. It is not front-loaded with useful information; it simply paraphrases the tool name. The single phrase offers no structural benefit and could mislead due to grammatical issues.

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 get operation with only three parameters and no output schema, the description still fails to provide basic context. It does not explain what an invoice schedule is, how it relates to invoices, or what the response format might be. An agent would have to rely on external knowledge or guess. The description is far from complete.

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 provides descriptions for all three parameters (scheduleId, altId, altType), so schema coverage is 100%. Per baseline, a score of 3 is appropriate since the schema carries the semantic weight. The description adds nothing beyond the schema, so it neither helps nor hurts beyond the baseline.

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 'Get an schedule' is a near-tautology of the tool name 'invoices_get_invoice_schedule'. It provides no additional specificity about what an invoice schedule is or what this operation does beyond the verb and resource already visible in the name. The grammar error ('an schedule') further reduces clarity.

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?

There is no guidance on when to use this tool versus the many sibling tools (e.g., invoices_list_invoice_schedules, invoices_update_invoice_schedule, invoices_cancel_invoice_schedule). No mention of prerequisites, alternatives, or exclusion criteria. The description is entirely silent on usage context.

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