dataverse_check_relationship_eligibility

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint false. The description adds the behavioral context that this is a pre-validation step to be used before creation operations, aligning with annotations and adding value without contradiction.

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 very concise: 4 lines with a clear front-loaded statement of purpose. Every sentence serves a purpose, no fluff.

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 simple tool with a single output (eligible bool), the description is mostly complete. It could mention that the table must exist, but the output schema fills in return details. Overall adequate for the complexity.

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 description only mentions check_type and refers to schema for valid values. Input schema already describes all parameters well (dataverse_url, table_logical_name, check_type). Description adds minimal extra meaning, meeting the baseline for 0% schema coverage.

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 pre-validates table relationship eligibility before creation. It distinguishes itself from sibling tools by specifying it's not for general queries or data reads.

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?

Explicitly says to call only immediately before dataverse_create_one_to_many_relationship or dataverse_create_many_to_many_relationship, and not for general queries or data reads. This provides clear when-to-use and when-not-to-use guidance.

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