Touchpoint

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

No annotations provided, but description discloses return structure: 'fresh snapshot with current states, value, supported actions, and description.' Clearly indicates this is a read-only inspection operation with current (non-cached) data.

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 tight sentences front-loaded with purpose, return value, and usage. Args section is brief but complete. Every sentence adds distinct value; no redundancy with structured fields.

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?

For a single-parameter lookup tool with output schema available, the description is comprehensive. It covers purpose, invocation context, parameter source, and output contents adequately.

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 has 0% description coverage. The Args section compensates by noting the element_id comes from 'find/elements results', providing critical provenance context that the raw schema lacks.

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?

Description states specific verb 'Get' with resource 'element' and scope 'by its ID with full detail'. The 'single' qualifier distinguishes it from plural siblings like `elements` or `find`.

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 when to use: 'inspect an element before calling the ``action()`` tool' and explains the value proposition: 'the actions list shows exactly which raw action names are available.' Names the sibling tool to use in sequence.

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