connects_resources

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior; the description adds the concrete scope of what is not supported (purchases, applications, payments) but no further operational traits such as pagination behavior or open-world data volatility. With annotations carrying the safety profile, this is adequate but not enriched.

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?

One sentence, front-loaded with the core action, and every phrase ('Read...', 'No purchases...') adds relevant scope. There is no wasted prose.

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?

The output schema and annotations cover return values and safety, and the description covers the high-level scope. However, missing parameter semantics and lack of comparison to sibling tools leave an agent to infer important usage details such as the filters view and fair_id selection.

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 for parameter meaning. It only hints at the collection/fair domain by listing those nouns, while view, limit, query, offset, and fair_id are left entirely to their schema titles and enums. That is insufficient for six parameters.

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 opens with the verb 'Read' and enumerates exact resource categories (jobs, mentorships, marketplace, stores, fairs), so an agent can tell what the tool operates on. It stops short of naming sibling tools, so it doesn't fully differentiate from overlapping tools like careers_jobs or connects_dashboard.

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 read-only framing and the explicit 'No purchases, applications or payments' exclusion give clear context for when the tool is appropriate. However, it never names an alternative or states when another sibling should be preferred, so the differentiation is only implied.

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