get_source

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

No annotations are provided, so the description must carry the full burden. It describes a read operation ('Get'), which implies no destructive side effects, but does not explicitly state permissions, error conditions, or safety guarantees. Minimal but adequate.

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 brief (5 lines), front-loaded with the key summary, and contains no unnecessary words. The Args/Returns sections are clearly structured and immediately useful.

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 tool is simple (1 param, read-only), an output schema exists (so return values are documented), and sibling tools are present, the description covers the essential retrieval purpose. It could mention error behavior (e.g., not found), but is otherwise complete.

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 schema provides no description for 'source_id' (0% coverage), but the description adds a format example ('e.g., source:abc123'), which clarifies the expected input beyond the schema's bare type string.

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 its verb ('Get') and resource ('a specific source by ID'), distinguishing it from siblings like 'list_sources' (which retrieves all) and 'create_source' (which creates new records).

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 does not explicitly state when to use this tool versus alternatives (e.g., 'use this when you have a known source ID'). It is implied by the name and parameter, but no direct guidance or exclusions are provided.

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