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

With no annotations, the description carries the full transparency burden. It discloses key behavioral aspects: returns comprehensive data, includes specific fields, and requires a domain filter to prevent returning the entire catalog. The example call illustrates usage. It does not mention pagination, output format, or read-only nature explicitly, but 'Return' implies read-only and the warning about scope is a strong transparency plus.

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 three sentences, front-loaded with the purpose, then usage, then a constraint and example. Every sentence adds value without redundancy. It is appropriately sized for a tool with one parameter and no complex nested structures.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description covers purpose, usage context, a scope warning, and an example. It misses only minor details like a note about the response being potentially large, but the emphasis on bulk processing already implies that. Overall it is complete enough for an agent to invoke correctly.

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 schema already fully documents the single parameter with an enum and description, so the baseline is 3. The description adds meaning by explaining why the domain is mandatory ('to prevent returning the entire catalog in one call') and showing a concrete example value. This goes beyond mere 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?

The description clearly states the tool returns the complete list of all data models within a specific domain, naming exact output content (names, subjects, descriptions, repository links). It distinguishes itself from sibling tools like get_data_model or search_data_models by focusing on the full-domain, bulk-oriented listing. The verb 'Return' plus specific resource makes the purpose unambiguous.

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 says 'Use this when the user needs a comprehensive structured overview of an entire domain for bulk processing, analysis, or selection,' which gives concrete usage context. It does not explicitly mention when not to use it or point to alternatives, but the context is clear enough for an AI agent to differentiate from more targeted tools. The mandatory domain filter is also stated as a usage constraint.

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