admin_get_canned_settings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies read-only, it does not explicitly confirm non-destructive behavior, idempotency, or any side effects. For a parameterless tool, this is 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 a single phrase with no wasted words. It is appropriately sized for a simple get operation with no parameters.

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?

The description is too minimal. It does not specify what 'canned response settings' includes (e.g., default response, permissions), and there is no output schema to clarify the return structure. Given the absence of annotations, more context is needed for an agent to correctly interpret the tool's output.

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?

There are no parameters, and schema coverage is 100%. The description adds no additional meaning beyond the schema. Baseline score of 3 applies per guidelines.

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 canned response settings' clearly indicates a read operation on a specific resource. It distinguishes from siblings like 'admin_list_canned_responses' (list vs get) and 'admin_get_settings' (general settings), though 'canned response settings' could be more precisely defined as global settings for the canned responses feature.

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. For example, it does not clarify when to use 'admin_get_settings' vs 'admin_get_canned_settings', or whether to use 'admin_list_canned_responses' first. No exclusions or preconditions are mentioned.

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