FilterElements

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the agent knows it's a safe, non-open-world read. However, the description adds no behavioral context: it doesn't explain what 'testing' means, what the output represents, or whether it returns boolean results per element. For a filter tool with 13 possible filter enum values, this is a significant gap.

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?

Very brief, but the single sentence contains grammatical errors ('an elements', 'criterias') and lacks front-loading of key information. While concise, it's under-specified rather than efficiently informative.

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 tool with 2 parameters (one required, one with 13 enum options), no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what 'testing' entails, what results are returned, or how filters are applied. An agent would struggle to use this tool correctly based on the available information.

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 description coverage is 0%, meaning neither the schema nor the description documents parameters meaningfully. The description mentions 'criterias' but doesn't explain the 'filters' array or 'elements' array beyond the schema's structural definitions. The 13 enum values for filters are listed in the schema but not elaborated in the description, leaving agents without guidance on filter semantics.

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 attempts to state a verb and resource: 'Tests an elements by the given criterias.' This suggests filtering elements, but the phrasing is grammatically broken and unclear. It doesn't clearly distinguish the tool from siblings like GetAllElements or GetElementsByType beyond a vague testing/filtering notion.

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. The description provides no context about appropriate scenarios or exclusions, leaving the agent to infer usage from siblings like GetElementsByType or GetAllElements.

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