Verify that material evidence metadata is present in submitted records to catch missing documents before applying for a Taiwan interior decoration permit.
Check material evidence metadata presence without judging material authenticity.
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | ||
| files | No | ||
| material_records | No |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must fully disclose behavioral traits. It only states that it does not judge authenticity, but says nothing about side effects, authorization requirements, or whether it is read-only. This omission leaves important behavioral uncertainty.
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 a single concise sentence with no redundancy. However, it could be restructured to front-load the key verb and resource more prominently, but overall it is efficiently short.
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 absence of annotations, output schema, and parameter descriptions, the tool definition is severely incomplete. The description does not explain return values, parameter usage, or provide enough context for correct invocation.
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% for three parameters, yet the description provides no explanation for any of them (text, files, material_records). The description adds no value beyond the schema's structural definition, failing to help the agent understand parameter meaning.
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 action ('check material evidence metadata presence') and includes a clarifying negative ('without judging material authenticity'), which distinguishes it from similar tools like check_claim_support or check_fire_compartment_evidence.
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 when to use it (when only metadata presence is needed) but does not explicitly state when not to use it or mention alternatives among siblings. The negative constraint provides some guidance but lacks directiveness.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.