blog

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

With no annotations, the description must carry the full burden of behavioral disclosure. It implies the tool is informational ('Company profile') but does not explicitly state that it is read-only, requires no authentication, or has no side effects. The lack of such details is a gap given the absence of 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 a single concise sentence that front-loads the purpose ('Who is Radixia?') and then enumerates the content areas. There is no redundancy or wasted words, making it an appropriately sized and well-structured description.

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 tool with no parameters, no annotations, and no output schema, the description adequately conveys the tool's purpose and content areas. It could be enhanced by describing the output format or whether the data is static, but given the simplicity, it is reasonably 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?

The tool has zero parameters, so the input schema fully covers the parameter space. The description adds no parameter-specific details, but the baseline for zero-parameter tools is 4, per the scoring rules.

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 identifies the tool as providing a company profile for Radixia, listing specific content areas (four capabilities, leadership, Labs, ecosystem, contacts). This distinctly separates it from sibling tools that handle ISC2026 agendas, sessions, and posts.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It simply states what the tool is, leaving the agent to infer its appropriate use.

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?

With no annotations, the description carries the transparency burden. It discloses that the agenda contains 'currently indexed' sessions and includes recorded talks, but does not discuss potential absence of data, response structure, or any side effects. For a read-only tool, this is adequate but not rich.

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?

Two sentences, front-loaded with the core content and a brief note on filtering. No wasted words, and all information is relevant.

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 low complexity (one optional parameter, no output schema), the description sufficiently covers what is returned and the available filter. It doesn't list every detail, but for a listing tool it is complete enough.

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 day parameter has an enum and description). The description adds only 'Optionally filter by day,' which is a minor restatement of the parameter's purpose, so it does not significantly augment 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 clearly states what the tool returns: the conference agenda with session blocks, times, halls, types, and speakers. It distinguishes from sibling get_conference_session by focusing on the overall program rather than a single session.

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 viewing the full agenda and notes optional day filtering, but it does not explicitly state when to choose this over get_conference_session or other siblings. There is no exclusion or alternative mention.

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?

With no annotations, the description carries the transparency burden. It discloses that transcripts are auto-generated and that matching is by partial title, which is useful. However, it doesn't mention behavior for multiple matches, output format, or potential large response size.

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?

Two sentences, no waste. The first states purpose, the second gives usage guidance. Perfectly front-loaded and efficient.

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 single-parameter tool with no output schema, the description covers the key aspects: what it returns, how to identify the session, and the preparatory step. It could mention return format, but that's a minor gap given the tool's simplicity.

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 provides 100% coverage with a clear parameter description and examples. The description adds redundant detail about partial title matching, but no extra semantic 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 clearly states the tool reads the full auto-generated transcript of one conference session by title. This distinguishes it from siblings like search_conference_transcripts (searching) and get_conference_agenda (schedule).

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?

It explicitly tells the agent to use search_conference_transcripts or get_conference_agenda first to find session titles, providing a clear workflow. It lacks explicit when-not-to-use conditions, but the context is unambiguous.

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?

With no annotations, the description carries the full burden. It states the operation is a read ('Read the full text'), which implies non-mutating behavior, but it doesn't disclose what happens for missing slugs, output format, or any other side effects. This is adequate for a simple read tool but lacks richer behavioral detail.

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, front-loaded sentence that directly states the action, resource, and how to get the required input. Every word earns its place with no filler or redundancy.

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 tool with one parameter, a clear schema, and no output schema, the description is complete. It tells the user what the tool does and how to obtain the required slug, covering the essential aspects for successful 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 100% with a clear example for slug. The description adds value beyond the schema by telling the user where to obtain the slug (list_posts or search_posts), which clarifies the expected parameter value and usage context.

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 reads the full text of a Radixia blog post by slug, using a specific verb ('Read') and resource ('blog post') with a precise identifier method ('by its slug'). It also distinguishes itself from siblings by referencing list_posts and search_posts for slug retrieval.

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 gives clear context on how to obtain the required slug ('get the slug from list_posts or search_posts'), which implies the prerequisite workflow. It doesn't explicitly state when not to use this tool, but the guidance is clear enough for selecting this over sibling tools.

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?

With no annotations provided, the description carries the full burden. It discloses the return shape (title, slug, date, tags, excerpt) which is useful, but it does not mention any side effects, permissions, rate limits, or whether only published posts are included. The read-only nature is implied by 'List', but not explicitly stated. This is adequate but not rich.

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, well-structured sentence that front-loads the action and resource, with a parenthetical for topics and return fields. Every clause adds value, and there is no wasted text.

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 tool is simple with two optional parameters and no output schema. The description covers the resource, scope, and return fields, which is sufficient for basic usage. Minor gaps include lack of explicit sorting direction (though 'most recent' implies it) and no mention of tag filtering, which is in the schema. Overall, it is complete enough for an agent to use 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 100% with both parameters fully described in the schema. The description adds no additional parameter-level context, so it does not go beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb 'List', the resource 'posts', and the scope 'most recent' on the Radixia blog. It also lists the exact fields returned (title, slug, date, tags, excerpt), distinguishing it from sibling tools like get_post (single post) and search_posts (search-based). This is a specific and unambiguous purpose.

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 this tool (when needing a chronological list of recent posts) but does not explicitly mention alternatives or exclusions. Sibling tools like search_posts and get_post exist, yet the description does not say 'use this instead of X'. It provides clear context but lacks explicit when-not-to-use guidance.

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?

No annotations are provided, so the description carries the burden. It discloses that tags come with post counts, which is useful output context, but does not mention any other behavioral aspects like sorting, pagination, or read-only implications. For a simple list operation, this is adequate but not rich.

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 that immediately states the action and result. Every word is meaningful, and there is no wasted text or unnecessary detail.

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 simple list tool with no parameters and no output schema, the description is largely complete. It specifies what is listed and the inclusion of post counts, covering the essential outcome. A small gap is that it does not describe the format of the response or any ordering, but given the simplicity, this is minor.

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, so the description is not required to explain parameter semantics. The baseline for 0 parameters is 4, and the description adds no confusion, so this score 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 lists topic tags from the Radixia blog and includes post counts. The verb 'List' and the specific resource 'topic tags' make the purpose unambiguous, distinguishing it from sibling tools like list_posts that handle posts.

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 clearly implies this tool is for retrieving tag information with counts, providing enough context for an agent to select it when tags are needed. However, it does not explicitly mention alternatives or 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?

With no annotations, the description carries the full burden. It discloses the return format (matching passages with session title, day/time/hall, recording timestamp) and a key search behavior (quoted phrases must match exactly). This adds meaningful behavioral context beyond the bare operation, though it does not cover all possible edge cases like result ordering or fuzzy matching.

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 concise sentences, front-loaded with the main purpose, then return fields, then a behavioral rule. Each sentence provides distinct value with no unnecessary words or repetition.

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 search tool with no output schema and no annotations, the description covers the search scope, content types, return fields, and a key behavioral constraint. It lacks details on result ranking, pagination, or failure behavior, but these are either covered by the schema or not critical for basic use. Overall, it is sufficiently complete 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?

Schema description coverage is 100% for both parameters, so the description need not add much. It does reiterate the query parameter's quoted-phrase behavior and adds context about the transcript corpus, but this is largely redundant with the schema's existing description. No new parameter-specific details are introduced.

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 performs full-text search over a specific resource: 147 auto-generated session transcripts from technical conferences. It specifies the types of sessions (keynotes, panels, vendor talks, research papers) and distinguishes itself from sibling search_posts by focusing on transcripts rather than posts.

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 through its scope but does not explicitly state when to use this tool versus alternatives like search_posts. There is no mention of when not to use it or any alternative recommendation, so guidance remains implicit rather than explicit.

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?

With no annotations, the description carries the full burden. It discloses that the search is full-text and covers all posts in specific fields, but it doesn't mention result ordering, pagination, read-only status, or other behavioral traits. The core behavior is clear, but deeper details are missing.

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, with the core purpose front-loaded and no redundant information. It is concise, efficient, 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?

The tool is simple, has no output schema, and the description covers purpose and usage. While it doesn't describe the return format, this is a minor gap given the tool's simplicity and the fact that the parameter behavior is well-documented.

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 describes both parameters (query and limit) with 100% coverage. The description adds value by specifying which fields are searched (title, excerpt, body) and provides example queries, enriching the semantics of the query parameter.

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 what the tool does: 'Full-text search across all Radixia blog posts (title, excerpt and body).' It uses a specific verb (search) and resource (Radixia blog posts), and the mention of fields distinguishes it from siblings like list_posts and get_post.

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 says 'Use this to find what Radixia has written about a topic' and provides concrete examples, giving clear context for when to use it. However, it doesn't explicitly discuss alternatives or when not to use it, so it falls 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.