ywm_get_recrawl_quota

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the implied read operation. It does not mention whether the tool is read-only, requires authentication, has rate limits, what it returns, or any side effects. The description adds no value beyond the tool name.

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 concise (three words), but this brevity comes at the cost of meaningful content. It is not misleading but fails to provide useful structure or explanation. A 3 reflects adequate conciseness but inadequate informativeness.

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 no output schema and no annotations, the description should compensate. It does not explain what recrawl quota is, what the output format is, or how the host_id parameter affects the result. The description is too minimal to be considered complete for a tool with a somewhat domain-specific concept.

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 100% (the single optional parameter host_id is described in the schema). The tool description adds no additional parameter information, so baseline 3 is appropriate. The description does not hurt but does not improve parameter understanding.

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 'Get recrawl quota' restates the tool name with a clear verb (get) and resource (recrawl quota). However, it does not explain what recrawl quota is or differentiate it from many other get_* tools among siblings (e.g., ywm_get_recrawl_task, ywm_get_original_text_quota). The purpose is minimally clear but lacks specificity.

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?

No guidance on when to use this tool vs alternatives. There is no mention of prerequisites, context, or exclusions. With many sibling tools performing related actions, the absence of any usage direction is a significant gap.

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