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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context by noting that the status 'reflects what SecureLend has recorded' and 'is not guaranteed to represent real-time lender decisions.' This is a significant behavioral caveat that informs the agent about data freshness, which the annotations do not convey. It goes beyond the minimum annotation coverage, earning a 4.

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 two sentences, about 30 words, and immediately states the main function. The first sentence front-loads the verb and resource, while the second adds a necessary caveat. There is no repetition of schema details or annotations, and every sentence contributes value. This is exceptionally concise and well-structured.

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 tool's simplicity (one required param, read-only, with an output schema), the description covers the key information: what is retrieved, how it is identified, and a critical non-real-time caveat. The output schema handles return values. The only gap is the misleading 'applicant email' reference, which detracts from completeness. Otherwise, it is sufficient for an agent to invoke the tool correctly if it relies on the schema and description together.

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 input schema has one parameter (applicationId) with a description that is clear: 'The unique ID of the application to track.' The tool description, however, claims it can retrieve status 'by applicationId or applicant email,' yet no applicantEmail parameter exists in the schema. This is misleading and could cause an agent to attempt invocation with an unsupported parameter. Since schema coverage is 100%, the description adds no useful semantics and actively introduces ambiguity, so a score of 2 is appropriate.

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's function: 'Retrieves the current enquiry/application status stored in SecureLend's system' by applicationId or applicant email. The verb 'retrieves' and the resource 'status' make the purpose explicit. However, it does not explicitly differentiate this from sibling tools like get_offer or get_multiple_offers, though the focus on 'status' rather than offer details provides some implicit distinction.

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 implies usage for checking application status, but provides no explicit guidance on when to use this vs alternatives like get_offer or get_multiple_offers. There are no 'use this when' or 'instead use X' statements. The mention of 'by applicationId or applicant email' hints at identification methods, but does not clarify when one identifier is preferred over the other. Overall, usage context is implied but not explicitly compared to siblings.

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