get_design_element

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 of behavioral disclosure. It states 'Get one design element' but does not mention whether the operation is read-only, what happens if the element is not found, permission requirements, or any side effects. The only added detail is 'with its documentation/description,' which hints at return contents but does not elaborate.

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, concise sentence that conveys the core purpose efficiently. The parenthetical adds a small amount of useful context without excessive padding. It is appropriately sized for a simple retrieval tool.

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 absence of annotations, output schema, and parameter descriptions, the description is minimal and incomplete. It does not explain the return structure beyond 'documentation/description,' nor does it clarify the role of project_id or the relationship between the two parameters. For a simple read tool, more context would be expected, especially since the tool is part of a large sibling family.

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 mention either parameter. The parameter names 'project_id' and 'element_id' are somewhat self-explanatory, but the description does not explain their relationship (e.g., why both are required, how to obtain them, or how they are used together). This leaves the agent to infer semantics from naming alone.

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 identifies the action ('Get') and the resource ('one design element'), and the qualifier 'one' distinguishes it from the sibling tool list_design_elements. The parenthetical '(with its documentation/description)' adds specificity about the return content.

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 implies usage for retrieving a single design element by ID, but it does not explicitly contrast with list_design_elements or state when to choose this tool over alternatives. No exclusions or prerequisites are mentioned; the context is only implicit.

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