newtqnia

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

Despite annotations already marking the tool as read-only and idempotent, the description adds substantial behavioral detail: administrators receive complete bilingual records including drafts, while other accounts only get a single locale with a canonical URL and never the article body. This goes well beyond the annotation hints.

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, front-loaded with the primary purpose, and every phrase adds distinct information. No redundancy or filler.

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, an output schema exists to handle return values, and the description covers role-based access, locale behavior, and draft visibility. Nothing essential is missing for an agent to select and invoke the tool correctly.

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 schema already documents both parameters with 100% coverage. The description adds extra value by instructing to pass the caller's language in locale and clarifying that locale is ignored for administrator tokens, reinforcing the meaning beyond the schema.

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 uses the specific verb 'Returns' with a clear resource: 'one published article.' It distinguishes from sibling tools by focusing on retrieval by ID and detailing role-based differences, making its purpose unambiguous.

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 the tool (fetching a single article by ID) and provides context about locale usage and admin vs. non-admin behavior. However, it does not explicitly contrast with alternatives like get_recent_news, so exclusions are only implicit.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds valuable behavioral context beyond annotations, such as the role-based response differences (bilingual vs. single locale) and the default time window.

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 long, front-loaded with the core purpose, and includes only essential information. There is no redundant repetition of schema fields or annotations.

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?

The description covers the main usage, role-based behavior, and key parameter semantics. It does not mention the limit parameter, but the schema provides that. Given the output schema exists and annotations cover safety, the description is sufficiently complete for an agent to select and invoke the tool correctly.

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 coverage is only 33% (only locale has a description), but the description compensates by explaining days ('past X days') and locale usage ('pass the caller's language'). It does not explain the limit parameter, which is mentioned in the schema but not described in text, so it earns a 4 rather than 5.

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 returns published news from a specified time window, using a specific verb ('Returns') and resource ('published news'). It also distinguishes itself from siblings like get_news_by_id by focusing on recent news lists rather than individual items.

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 provides clear context for when to use the tool (to fetch recent published news) and includes role-based usage details (admins vs. other accounts). However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of a 5.

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

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes far beyond by disclosing role-based access (admin vs other accounts), locale handling, draft visibility, and explicit content exclusions (never event bodies or introduction/conclusion). This is rich behavioral context.

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 compact despite covering complex role-based behavior. It front-loads the core purpose in the first sentence and efficiently packs details into the second. Every clause earns its place with no filler.

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 complexity (role-based responses, locale sensitivity, content filtering), the description covers all critical aspects. The presence of an output schema handles return-value details, so the description's focus on access rules and exclusions makes it 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 coverage is 100%, so the baseline is 3. The description mentions passing the caller's language in locale, which adds slight context, but mostly reiterates the schema's own description. No significant new parameter semantics are added.

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 opens with 'Returns one published timeline,' which is a specific verb+resource statement. The tool name and title also align, and the detailed role-based behavior clearly differentiates it from sibling tools like get_news_by_id or search_explainers.

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 makes clear this is for fetching a single timeline by ID, providing strong contextual guidance. It does not explicitly name alternatives or exclusions, but the purpose is distinct enough that no alternative is needed. This fits 'clear context, no exclusions'.

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

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

The description adds valuable behavioral context beyond the annotations: it explains the visibility difference between administrator and non-administrator tokens, the locale parameter's behavior, and that results include a canonical URL. This is useful supplementary detail to the readOnly and idempotent hints provided by annotations.

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 three sentences long, front-loaded with the core purpose, and each sentence adds meaningful information. It is tight and free of redundancy, making it easy for an agent to parse quickly.

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 output schema exists and annotations are present, the description covers all necessary aspects: search scope, role-based behavior, locale handling, canonical URL, and a usage recommendation for duplicate avoidance. It is fully sufficient for the tool's complexity.

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 description clarifies the 'query' parameter by listing the searchable fields (title, slug, summary, content), which is not in the schema. It also explains the 'locale' parameter's role and administrator override. Only 'limit' lacks description, but its schema constraints and default are sufficient. With schema description coverage at 33%, the description effectively compensates.

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 uses a specific verb ('searches') and clearly identifies the resource ('explainers') and the exact searchable fields (English/Arabic title, slug, summary, content). This distinguishes it from sibling tools like search_terminology and get_news_by_id.

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?

Explicitly states when to use this tool ('should call this before creating a new explainer to avoid duplicates') and explains role-based behavior (administrators vs other accounts) and locale handling. It does not explicitly name alternative tools, but the context is clear enough to guide selection.

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

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond these: normalized and case-insensitive matching, role-based visibility (draft vs. published, both languages for admins), locale handling for non-admins, and the inclusion of a canonical URL. This goes beyond the annotations, though it does not cover every behavior (e.g., pagination), but with annotations carrying the safety profile, a 4 is justified.

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 remarkably concise—only two sentences—yet packs in the core search behavior, usage guidance, role-based differences, and locale handling. Every sentence earns its place, with the primary purpose front-loaded. No redundancy or filler.

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?

The description covers purpose, usage, behavioral nuances, and key parameter semantics. With an output schema present, the description does not need to explain return values. It addresses the tool's complexity (role-based results, locale, canonical URL) adequately. Minor missing aspects like limitation/pagination are either obvious from schema or unnecessary. A score of 4 reflects strong completeness without being exhaustive.

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 only 33% (locale), but the description compensates for query by explaining it searches by English term, Arabic term, abbreviation, or slug. It also references locale by saying 'pass the caller's language in locale.' The limit parameter is not explicitly described, but its schema includes defaults and bounds, making its semantics reasonably clear. This is above baseline due to the added query context, though limit remains a minor gap.

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: 'Searches terminology by English term, Arabic term, abbreviation, or slug using normalized, case-insensitive matching.' This specifies the verb, resource, and search fields, and distinguishes it from sibling tools like search_explainers, which search a different domain. The role-based detail further clarifies scope.

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 provides explicit guidance: 'should call this before creating a new term to avoid duplicates.' It also explains role-based use cases (administrators vs. other accounts). However, it does not explicitly mention alternatives or when not to use the tool, though the sibling list implies different domains. This is clear context but lacks explicit exclusions, so a score of 4 is appropriate.

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

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

Annotations fully declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the specific return content (health and timestamp) but does not disclose additional behavioral traits such as rate limits or error conditions. With comprehensive annotations, a score of 3 is appropriate.

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, clear sentence that immediately conveys the tool's purpose without any redundant words or filler. It is perfectly 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 (no parameters), a complete output schema, and annotations that cover safety and idempotency, the description adequately conveys what the tool returns. There are no gaps in the context needed for an agent to use it correctly.

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 has zero parameters and the schema confirms an empty object, so the description does not need to provide parameter details. The baseline for zero-parameter tools is 4, and no additional parameter semantics are necessary.

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 uses a specific verb ('Returns') and clearly identifies the resource ('health and timestamp of the NewTqnia server'), distinguishing it from sibling tools focused on news and search. It is immediately clear what the tool does.

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 usage context is clear: this is a server health check, distinct from the content retrieval siblings. However, it does not explicitly state when to use it (e.g., before other API calls) or mention any exclusions, but the uniqueness of the tool makes the intended usage obvious.

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