Get Contact

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

Description does not add behavioral insight beyond annotations. Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description adds no extra context about side effects or requirements.

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?

Description is a single, clear sentence with no superfluous words. Front-loaded with essential information. Appropriate for the tool's simplicity.

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 retrieval operation, one parameter, zero output schema, and comprehensive annotations, the description is complete. No further context is needed.

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?

Only one parameter (id) with schema description 'Contact ID'. Description mentions 'by ID' but adds no semantic detail beyond what the schema already provides. Schema coverage is 100%, so baseline 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?

Description clearly states 'Get a single contact by ID', specifying verb (get), resource (contact), and parameter (ID). This distinguishes it from sibling tools like lexware_list_contacts (list) and lexware_create_contact (create).

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 explicit guidance on when to use this tool versus alternatives, but the simple nature of fetching by ID implies usage. It does not mention when not to use or provide alternative tool names.

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