pbs_notification_matcher_fields

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

No annotations provided, description indicates read-only but contradicts itself by saying 'No params' while schema has an optional parameter. Lacks details on side effects, auth, or rate limits.

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 concise and front-loaded with key info, but the inaccurate 'No params' undermines its effectiveness.

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?

With output schema present, return values are covered, but omission of the optional parameter from description leaves a significant gap for a tool with one param.

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?

Description incorrectly states 'No params' despite a documented optional parameter. Adds no value and misleads, scoring below baseline for high schema coverage.

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?

Clearly states it lists all known metadata field names for matcher match-field rules with examples. Distinguishes from sibling tools like pbs_notification_matcher_field_values.

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?

Implies read-only use and mentions config requirement, but does not explicitly contrast with alternatives like pbs_notification_matcher_field_values or state when not to use.

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