get_primitive

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

No annotations are provided, so the description carries the burden. It describes a read-only metadata retrieval and lists what is included, but does not disclose any side effects or safety traits beyond that. No contradictions with annotations since none exist.

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, compact sentence that efficiently conveys the tool's purpose and usage, with no extraneous information.

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 complexity of the metadata (parts, props, accessibility, example), the description lists these components, providing a clear sense of what is returned. No output schema, but the listing suffices. It could be improved by hinting at output structure, but it is largely complete for a getter with one parameter.

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 100% for the single parameter 'name', which includes examples and case-insensitivity. The description does not add additional parameter semantics beyond the schema, so baseline 3 is appropriate.

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 states it retrieves full metadata for a Radix primitive, listing specific components (composable parts, props, accessibility contract, minimal example). It distinguishes itself from siblings by being comprehensive, while get_a11y_contract focuses on accessibility and list_primitives lists all primitives.

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 instructs 'Use before writing or editing any Radix component,' providing clear context. It does not mention exclusions or alternatives, but sibling tool names (get_a11y_contract, list_primitives) help the agent infer when to use alternatives.

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