funder_compliance

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It hints at an output of 'actionable issues' and implies a compliance checking function, but does not explain side effects, permissions, whether it is read-only, or the nature of the output format. This is insufficient for an unannotated tool.

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 extremely short, but this is under-specification rather than conciseness. It lacks structure and does not earn its place because it leaves out essential information. The single phrase provides no actionable detail for an agent.

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 five optional parameters, no annotations, and a minimal description, the tool is grossly incomplete. It does not explain return values (despite an output schema existing), how parameters interact, or what the tool accomplishes in a way an agent can rely on. The description is far too sparse for a tool with this 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?

Schema description coverage is 0%, so the description must compensate for five parameters. It only lists domain terms (IDs, awards, licenses, ORCID) without mapping them to any specific parameter or explaining their meaning. No parameter name appears in the description, leaving all parameter semantics unexplained.

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 is a noun phrase rather than a clear verb+resource statement. It indicates the tool relates to funder/award compliance and mentions topics like IDs, awards, licenses, and ORCID, but does not specify what action it performs (e.g., retrieve, validate, check). It also fails to distinguish itself from the sibling tool 'export_funder_issues'.

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 description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or situations where another tool (like export_funder_issues) would be preferable.

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