get_element

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

Discloses that the tool raises an error if the element is not found, which is key behavioral information. With no annotations, the description carries the full burden and adds this important detail.

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 sentence with no wasted words. It is front-loaded with the key action and resource. However, it could be slightly more structured by separating the retrieval from the error behavior.

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 that an output schema exists, return values are not needed. However, the description fails to explain the 'kind' parameter or any filtering logic. The tool has two required params and an enum, so more context would be beneficial.

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 does not explain the purpose of the 'kind' parameter or provide any additional meaning beyond the schema. The tool has two required params, but only 'uuid' is hinted.

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 action 'Retrieve an element by UUID' and notes the behavior 'Raises if not found'. This distinguishes from sibling tools like delete_element or create_wall.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the operation is straightforward, there is no discussion of alternatives like get_attributes or context for choosing this tool.

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