source_and_rights_policy

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

With no annotations, the description carries the full burden; "hard-coded" usefully signals that the result is static and not configurable per call. However, it does not describe what the safeguards contain, whether they are prose or structured data, or how an agent should apply them, so behavioral disclosure is partial.

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?

A single front-loaded sentence with no filler or redundancy. Every word earns its place and the key qualifier ("hard-coded") appears immediately.

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 simple zero-parameter read tool this is close to adequate, but with no output schema and no annotations the description leaves the return shape unspecified — an agent cannot tell whether it gets prose, a rules list, or a boolean gate. One clause on what the safeguards look like would close the gap.

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 tool takes zero parameters, which is the baseline-4 case; there is nothing parameter-wise the description needs to explain. It correctly implies a parameterless call by describing a fixed, project-level policy.

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?

States a specific verb ("Return") and a specific resource ("the project's hard-coded SSRN/Elsevier access safeguards"), which is clearly distinct from sibling tools like search_papers or find_open_access_link. It does not explicitly name those siblings, but the resource is unique enough that confusion is unlikely.

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?

There is no statement of when to call this versus alternatives such as find_open_access_link or get_ssrn_reference_link, and no prerequisites or exclusions are given. An agent must infer that this is a policy-lookup to consult before handling SSRN/Elsevier sources.

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