Retrieve the clean text content of a president.az page from its URL, removing page markup for easier reading or processing.
Clean text of a president.az page. / president.az səhifəsinin təmiz mətni.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It hints that the page is stripped to 'clean text' but says nothing about return format, error handling for non-president.az URLs, rate limits, or whether the fetched page must already exist.
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?
Very short and front-loaded, with no filler. The bilingual restatement is duplicative for a single reader but defensible for a multilingual audience.
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 one-parameter fetch tool with no output schema and no annotations, the description conveys the core operation but omits the return shape and any failure conditions. Minimally adequate rather than 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?
Schema description coverage is 0% and the single 'url' parameter is undocumented. The description only weakly constrains it by naming president.az, without stating that the URL must belong to that domain or what format it expects.
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 ('clean text') and resource ('president.az page'), so an agent can tell it extracts page text rather than searching. It does not explicitly distinguish itself from the sibling president_axtar, which is a search tool, leaving the boundary implicit.
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 versus president_axtar or the other *_metn siblings. The agent must infer that this is the fetch-a-known-URL tool from the name and parameter alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.