filter__get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The 'Get current' wording clearly signals a non-destructive read operation, but the description does not disclose what the returned configuration looks like, whether it reflects a persisted or computed state, or any error behavior.

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 sentence with a useful category prefix and no filler. It is concise and front-loaded, though it omits some usage and behavioral nuance that would make it more helpful.

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 getter with no output schema, the description is nearly complete: an agent can infer that calling it requires no inputs and returns the current filter configuration. The main gap is the absence of any detail about the return shape or possible edge states, but the low complexity makes this a minor issue.

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 and schema description coverage is 100%, so there is no hidden or undocumented parameter burden. The description still adds a small amount of context by naming the target resource, 'tool filter configuration', which is sufficient for a parameterless call.

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 uses the verb 'Get' and the object 'current tool filter configuration', clearly identifying a read operation on a specific resource. The word 'current' plus the sibling names filter__update and filter__reset make the basic distinction from mutating operations apparent, though it does not explicitly name them.

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?

The description implies that this tool is for reading the filter configuration rather than updating or resetting it, but it never states when to use this tool versus the filter__update or filter__reset alternatives. There is no explicit when/when-not guidance or mention of prerequisites.

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