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

No annotations are provided, so the description carries the full burden, yet it discloses no behavioral traits at all — no read/write profile, no permissions, no return behavior. A single noun phrase offers zero behavioral context for a tool with no structured safety hints.

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 phrase is short but under-specified rather than concise — it fails to say what the tool does or returns. Brevity here reflects missing information, not efficient communication.

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?

With no annotations, no output schema, and no parameters, the description is the only carrier of meaning, and it does not explain what the tool returns or when to call it. For a zero-param tool the bar is low, but the description still leaves the agent unable to predict the result set.

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 takes zero parameters, which sets the baseline at 4 regardless of description content. There is no schema description to compensate for or explain, so no gap exists on this dimension.

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 is a bare noun phrase ('Source of basic administrative data') that restates the resource implied by the name get_sources rather than stating a verb+resource action. It never says the tool retrieves, lists, or returns anything, and it gives no differentiation from siblings like get_basic_profile or get_territory_hierarchy.

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?

There is no when-to-use guidance, no alternative named, and no context for selecting this tool over the sibling get_basic_profile or search_territory_knowledge. The description provides nothing to route an agent's decision.

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