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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the word 'current', implying values may change over time, which is useful context. No further behavioral traits are disclosed, but the combination of annotations and output schema keeps this at an adequate level.

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, front-loaded sentence with no wasted words. It is appropriately concise for a parameterless read-only tool, though the sparse information could be enriched with minimal usage context without hurting clarity.

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 0-parameter read-only tool with an output schema, the description is minimally adequate. It states what is returned (filter values) and their dynamic nature, but does not place the vocabulary in the broader filtering workflow or whether it is global/scoped. The output schema fills return format details, but overall completeness is basic.

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 has zero parameters, so the baseline is 4. There is nothing for the description to add beyond what the (empty) input schema already conveys.

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?

Description states a specific verb ('Get') and resource ('filter values'), clearly distinguishing from entity-specific siblings like get_intel or list_projects. The phrase 'current supported filter values' makes the purpose unambiguous, though it could explicitly mention the domain or context.

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 its siblings or alternatives. An agent must infer that filter vocabulary is a prerequisite or reference for other calls; there are no explicit when-to-use instructions or exclusions.

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