Get Invoice Settings

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that — no mention of permissions required, scope of the settings returned, or any caching/side-effect nuance.

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?

Four words, front-loaded, and free of padding — but the brevity comes at the cost of under-specification rather than true conciseness. It is not wasteful, but it also does not earn its place beyond the title.

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 zero-parameter, read-only tool with no output schema and full annotation coverage, the description is minimally sufficient to invoke correctly. It nonetheless leaves the agent guessing about what the settings contain and how this relates to update_invoice_info, which is the one gap worth closing.

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 tool takes zero parameters, which is the baseline-4 case per the rubric. There is nothing for the description to clarify regarding inputs, and it correctly implies a global, unparameterized read.

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 adds one clarifying word over the title ('company'), indicating this returns company-level invoice configuration rather than per-invoice data. However, it is essentially a restatement of the title 'Get Invoice Settings' and does not distinguish itself from the sibling update_invoice_info beyond the read/write verb difference. Purpose is inferable but vague.

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 about when to call this tool versus alternatives, nor any prerequisites or context. An agent must infer from the name alone that this is the read counterpart to update_invoice_info.

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