settings_get

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

No annotations are provided, so the description carries the burden. It describes the return type (settings) and lists the specific settings. It also includes a usage hint about date format, which aids transparency. No contradictions.

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?

Two sentences: first states the purpose and lists what is returned; second gives specific usage guidance. No unnecessary words. Front-loaded with key information.

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 simple get operation with one required parameter and no output schema, the description is complete. It tells what the tool returns, the context (per-company import settings), and a practical reason to use it (check date format). No gaps.

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?

Schema coverage is 100% (companyId is described as 'Company id from companies_list.'). The description does not add additional semantic meaning beyond what the schema provides, but the schema is already clear. Baseline 3 is appropriate.

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 states it returns per-company import settings and lists specific fields (dateFormat, document-number behavior, etc.). The verb 'Returns' clearly indicates a read operation, and the resource (import settings) is distinct from sibling tools like settings_update.

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?

Explicit guidance: 'Check dateFormat before importing — CSV date columns must match.' This tells the agent when to use this tool (before importing) and why it's important. While it doesn't explicitly mention when not to use or alternative tools, the context is clear.

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