get_task_relay_job_contract

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

No annotations provided, so description carries full burden. It indicates a read-only operation ('get', 'discovery only'), but does not disclose behavioral traits such as authentication requirements, rate limits, error handling (e.g., if contract not found), or whether it has any side effects.

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?

Description is a single concise sentence that front-loads the action and resources. No wasted words. However, it could incorporate more context (e.g., return format) without significantly lengthening it.

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?

No output schema, so description does not specify the return format or structure. While the tool is simple (one parameter, single contract retrieval), the lack of detail on what the contract contains or response behavior leaves gaps in completeness.

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 coverage is 100%, with the single parameter 'franchise_id' fully described by an enum of allowed values. The description does not add any additional meaning beyond what the schema provides, meeting the baseline for high 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?

Description clearly states 'Get exact public Task Relay job contract for F1-F5 (discovery only)', specifying the resource, action, and scope. It distinguishes from siblings 'find_task_relay_job' and 'list_task_relay_jobs' by indicating it retrieves a specific contract rather than a list or search.

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?

Description mentions 'discovery only', implying it's not for production use, but does not explicitly state when to use this tool vs alternatives or provide when-not-to-use guidance. No mention of prerequisites or required permissions.

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