query_gcat_psatcat

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

Annotations are absent, so the description bears full burden. It describes filter chaining and requirements but does not disclose return format, error behavior, or performance implications. It mentions the default limit but lacks a complete behavioral profile.

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, with a clear opening sentence and structured Args. It is front-loaded with purpose and important constraints. Minor redundancy in 'advanced chainable filters' and 'Filters are applied sequentially,' but overall efficient.

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?

The description lacks information about return values (no output schema) and does not clarify how results differ from sibling `get_gcat_psatcat`. Given the number of parameters and complexity, additional context on output format or usage with other tools would improve completeness.

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 input schema has 0% description coverage, but the description's Args section explains each parameter (name, category, object_class, etc.) with examples and context, adding substantial meaning beyond the schema's titles and types.

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 'Query GCAT PSATCAT with advanced chainable filters,' using a specific verb and resource. It distinguishes from sibling tools like `get_gcat_psatcat` (which likely fetches without filters) and `query_gcat_satcat` (different catalog).

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 explicitly requires at least one filter parameter ('At least one filter parameter must be provided') and explains sequential application. It suggests using `list_gcat_options()` for full code details, providing context for usage. It does not explicitly state when not to use, but the guidance is clear.

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