get_component

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

With no annotations, the description explains the return content but doesn't explicitly state read-only behavior or potential error conditions. Adequate but could be more transparent about side-effect-free nature.

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?

Two sentences, both essential and front-loaded with the primary purpose. No extraneous 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 the simple single-parameter tool with no output schema, the description covers what the tool returns and how it relates to the sibling, making it fully adequate.

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 already describes the 'name' parameter; description adds useful cross-reference to 'list_components' for obtaining valid names, enhancing the value beyond the schema.

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 the tool retrieves the full schema for a single petal_components component, listing specific details (attrs, slots, defaults, etc.) and contrasting with sibling list_components.

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 advises calling when writing a Phoenix LiveView component reference to ensure attrs and slots match, providing strong when-to-use guidance. Does not explicitly state when not to use it, but the context implies it.

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