mayotte_get_sources

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

With no annotations, the description must carry the burden of disclosing behavior. 'List' implies a read-only operation with no side effects, but it does not mention authentication requirements, data freshness, or any potential limitations. The description is minimal and lacks explicit behavioral details.

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 a single, concise sentence that conveys the essential information without any fluff. It is well-structured and directly addresses the tool's purpose.

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's simplicity and lack of parameters or output schema, the description is mostly complete. It tells the user what the tool does, though it does not elaborate on what constitutes 'curated official and high-value sources' or how the list is structured. This is a minor gap but not critical for basic usage.

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, so there is nothing to explain. The description does not need to add parameter meaning, and the lack of parameters is fully reflected in the schema. This dimension is not applicable and scored as perfect.

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 the tool lists curated official and high-value sources for Mayotte, using the verb 'list' and specifying the resource. It distinguishes itself from sibling tools like search, get, and find by focusing on a curated list of sources.

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 indicates the tool returns a list of sources but provides no explicit guidance on when to use this tool versus alternatives like search_data_gouv or get_dataset. It implies usage for obtaining curated sources but lacks comparative context.

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