element_definitions_list

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns id, title, and property_keys, but does not disclose other behavioral aspects such as pagination or ordering. No contradiction with annotations.

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?

Three short sentences, each adding value. First sentence defines purpose, second gives usage hint for the output, third clarifies read-only nature and alternative for mutations. No wasted words.

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 no output schema, the description partially describes the return value (id, title, property_keys) but omits details like pagination, completeness of data, or any ordering. The 'site' parameter is left unexplained. It covers the core but has gaps.

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?

Input schema has one required parameter 'site' with no description. Schema description coverage is 0%, and the description does not explain what 'site' represents or how to construct its value. This is a significant gap that leaves the agent without guidance on a crucial required parameter.

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 the tool lists element definitions with specific fields (id, title, property_keys). Connects purpose to sibling tool element_create by specifying how the returned id is used. Distinguishes from mutation tools by noting they are deferred to voog_admin_api_call.

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?

Explicitly states the tool is read-only and that mutating definitions should be handled via voog_admin_api_call. Provides clear when-to-use and when-not-to-use guidance with a concrete alternative.

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