get_spam_filter

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

With no annotations, the description must convey behavioral traits. The verb 'Get' implies a read-only operation, but the description does not explicitly state that it is non-destructive, lacks side effects, or requires any specific permissions. The context is adequate but not fully transparent.

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 concise, consisting of three short lines: a purpose statement, a list of filter names, and a clarification for one filter. Every sentence adds value, and the structure is front-loaded with the main action.

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 getter tool with one parameter and no output schema, the description covers the input adequately but lacks details on the return format. It does not specify what 'settings' are returned for each filter type, which could be needed for correct invocation.

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 0%, so the description fully explains the 'filter_name' parameter by listing allowed values: 'blacklist|links|caps|symbols|repetitions|emotes'. However, it only describes the 'blacklist' option in detail; the meaning of other filters is left unexplained. This adds some value beyond the schema but is incomplete.

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 clearly states 'Get a spam-protection filter's settings', specifying the verb 'Get' and the resource 'spam-protection filter's settings'. It also lists the allowed filter names, distinguishing it from sibling tools like 'update_spam_filter' which modify settings.

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 is provided on when to use this tool versus alternatives like 'update_spam_filter' or 'add_banned_phrases'. The description does not mention any conditions, prerequisites, or exclusions.

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