catalog

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

No annotations are provided, so the description must carry the full burden. 'Discover' implies a read-only operation, but no explicit mention of safety, side effects, or behavior is made. Pagination (cursor, limit) and filtering capabilities are not disclosed, leaving the agent unaware of how the tool behaves.

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 short but under-specifying. While brevity is good, the single vague sentence does not earn its place because it omits essential information. The structure is fine, but the content is too sparse to be useful.

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?

Given the tool's complexity (3 parameters, nested filters, an output schema, and numerous sibling tools), a one-sentence description is far from complete. It does not explain the purpose of kind or filters, nor the context_id requirement. The agent cannot confidently invoke the tool based on this description.

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%, and the description adds no meaning to parameters like context_id, filters, or kind. It merely lists a few enum values already visible in the schema, failing to explain their semantics or usage. For a tool with a complex nested filter object, this is a critical gap.

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 'Discover' and names specific catalog entities (models, properties, relations, operators), giving a clear sense of what the tool provides. However, it omits other kinds present in the schema (e.g., object_types, semantic_classes, limits) and does not distinguish from sibling tools with overlapping functionality.

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 provides no guidance on when to use this tool versus alternatives like object_query or object_resolve. It lacks any context about appropriate scenarios, prerequisites, or exclusions, leaving the agent without decision support.

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