get_contact_sources

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

No annotations exist, but the description correctly implies a read-only listing operation by stating it 'returns the list of sources... with their IDs'. It could mention static nature or cache behavior, but for a simple list, this is sufficient.

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 concise sentences: first states purpose, second gives examples, third provides actionable guidance. No wasted words, and the structure is logical and front-loaded.

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 zero parameters and no output schema, the description fully covers the tool's behavior: it lists sources with IDs, gives examples, and explains when to use it. Nothing essential is missing.

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 tool has no parameters and the schema is empty, so the description adds value by explaining the return type and usage context, which helps the agent understand what to expect 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 explicitly states 'List all available contact/lead sources in Propstack' and provides concrete examples like 'Immobilienscout 24', 'Website', 'Empfehlung', making the purpose immediately clear. No sibling tool has a similar function, so it is distinct.

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?

The description directly advises using this tool to look up valid source IDs before creating or updating contacts with client_source_id, providing explicit when-to-use guidance and practical context.

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