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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile, so the description correctly doesn't restate safety. It adds genuine value by disclosing what is NOT published (cash check size, duration, funding guarantee, review deadline), preventing the agent from expecting or re-querying for those fields.

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?

Three short sentences, front-loaded with purpose, then scope limits, then the commitment caveat. No filler, though the negative-information sentence is slightly dense and could be split for scanability.

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 zero-param, read-only tool with no output schema, the description gives enough: what is returned (offer plus submission rules) and what is explicitly absent. A brief pointer to validate_submission or submit_project as the next step would make it fully complete.

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, so there is no schema semantics for the description to supplement; baseline for a no-param tool is 4. Nothing is missing on this dimension.

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 and resource: read the published builder offer and submission rules from 'Creditable'. It is clearly distinguishable from siblings submit_project and validate_submission by being the read-only counterpart, though it never names those siblings explicitly.

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 closing line 'Applying creates no commitment' implies this should be read before submit_project, but the description never states when to call it, when not to, or that submit_project/validate_submission are the alternatives once the rules are understood. Usage is implied rather than directed.

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