Get Provider

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

Annotations (readOnlyHint=true, openWorldHint=true, idempotentHint=true) already declare safety and idempotency. The description adds no additional behavioral context such as return format, error behavior, or implications of fetching a provider. It simply restates the schema-level operation, providing no value beyond the annotations.

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?

A single, concise sentence that is perfectly sized for this trivial operation. No fluff, unnecessary qualifications, or repetition. It earns its place with immediate clarity.

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 low-complexity get-by-id tool with strong annotations and full schema coverage, the description is minimally adequate. However, it lacks any hint about what a 'provider' is, what the response contains, or potential error conditions (e.g., non-existent id). No output schema exists, so a brief note on return shape would have improved completeness.

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?

The input schema has 100% coverage with a clear description for provider_id ('The provider id to fetch'). The description's 'by id' adds no new meaning beyond what the schema already states, so the baseline of 3 applies.

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 'Fetch a provider by id' clearly states the verb (fetch), the resource (provider), and the identifier parameter (id). It distinguishes itself from sibling tools like lyzr_get_providers_by_type (by type) and lyzr_get_provider_credential (credentials), though it does not explicitly name these alternatives.

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 guidance is provided on when to use this tool versus the many related tools (e.g., lyzr_get_providers_by_type, lyzr_list_provider_credentials_by_user, lyzr_get_provider_credential). The description offers no exclusions, prerequisites, or contextual decision-making help.

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