fetch_datasources

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions pagination parameters but doesn't disclose critical traits like whether this is a read-only operation, rate limits, authentication needs, or what the output format looks like (e.g., list structure).

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 extremely concise with just one sentence that front-loads the core purpose ('List datasources') followed by parameter mention. Every word serves a purpose, with no wasted text.

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?

For a list operation with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the return format, pagination behavior, or how it differs from similar fetch tools, leaving significant gaps for an AI agent.

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?

Schema description coverage is 0%, so the description must compensate but only vaguely mentions 'Optional per_page, page' without explaining what these parameters do (e.g., per_page controls items per page, page selects page number). This adds minimal value beyond the bare 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 clearly states the action ('List') and resource ('datasources'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'fetch_datasource_entries' or 'get_datasource', which might cause confusion about scope.

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 guidance is provided about when to use this tool versus alternatives like 'get_datasource' (for a single datasource) or 'fetch_datasource_entries' (for entries within a datasource). The description only mentions optional parameters without context.

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