get_data

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does not mention authentication requirements, rate limits, or what 'metadata' in the schema means. The description adds no behavioral context beyond what the schema already states.

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 sentence, front-loaded with the action ('Retrieve data'), and wastes no words. However, 'custom data source' is under-specified, which slightly reduces clarity.

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 output schema and no annotations, the description should elaborate on return values and behavioral context. It fails to mention the meaning of 'metadata', the nature of the data source, or potential error conditions, making it incomplete for a 4-parameter tool.

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 input schema describes all four parameters with clear descriptions, so baseline is 3. The description's mention of 'filtering and pagination' adds minimal extra meaning by hinting at the filter and limit parameters, but does not explain outputMode or includeMetadata 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 uses the specific verb 'Retrieve' with the object 'data from your custom data source', clearly indicating the tool's function. It implicitly distinguishes from the sibling 'get_system_info' by focusing on custom data, but 'custom data source' is vague and lacks detail.

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 phrase 'with optional filtering and pagination' implies when to use the tool (when you need data with these capabilities), but there is no explicit guidance on alternatives or when not to use it. No comparison with the sibling tool 'get_system_info' is provided.

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