get_metaobject_definitions

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Fetch metaobject definitions' and does not disclose pagination behavior, return format, ordering, or whether it is a read-only operation. 'Fetch' implies a read, but no explicit safety or side-effect information is given.

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 a single, direct sentence with no filler or redundant content. It is appropriately short for a simple read operation, earning a high score for conciseness.

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 tool has only two documented parameters and no output schema, so the description needs to explain return values or scope, but it does not. It adequately conveys the basic intent but leaves gaps about what a metaobject definition is, what the response contains, and how pagination works beyond the schema's parameter descriptions.

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 provides 100% coverage with descriptions for both parameters: 'Cursor for pagination' for after, and 'Number of definitions to fetch (default: 50)' for first. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 'Fetch metaobject definitions' uses a specific verb ('fetch') and a clear resource ('metaobject definitions'). It distinguishes from sibling tools like get_metaobjects (which fetches instances) and create/update/delete_metaobject_definition, making 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?

There is no guidance on when to use this tool vs alternatives. No mention of when to prefer this over get_metaobjects or the definition CRUD tools, nor any prerequisites or context. The description is purely a statement of action without usage context.

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