get_sales_agent_config

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds value beyond that by stating the API key requirement and that the result is scoped to the authenticated account, plus the read-before-write rationale. It stops short of describing error behavior or failure modes, so it is not a full 5.

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?

Three short paragraphs, front-loaded with the payload the tool returns, followed by usage routing and then the behavioral notes. No sentence is padding; each one adds routing or safety 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?

With no output schema and no parameters, the description carries the burden of saying what comes back, and it enumerates the returned fields. Combined with the account scoping and API key note, an agent has everything needed to call it correctly.

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. The description explicitly confirms 'takes no parameters', which is consistent with the empty schema and leaves no ambiguity about whether filters are expected.

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?

States a specific verb and resource (fetch the AI sales agent's current settings) and enumerates the concrete field set returned: enabled flag, booking link, offer price, reply limits, confidence threshold. An agent can distinguish it from update_sales_agent_config and the other sibling get_* status tools at a glance.

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?

Explicitly names the alternative (update_sales_agent_config) and gives the two conditions that select this tool: read before updating so a single-field change doesn't clobber the rest, and check the enabled flag before expecting the agent to act. This is exactly the when-to-use/when-not guidance the dimension asks for.

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