get_site_info

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

With no annotations provided, the description carries the full burden for disclosing behavioral traits. It states 'Anonymous', which signals that no authentication is required—a useful transparency note. 'Get' implies a read-only operation with no side effects, but the description does not explicitly confirm this or mention any rate limits, caching, or variability in the returned configuration.

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—two short phrases—and front-loads the primary action ('Get site configuration') before details and access mode. Every word earns its place; the only minor weakness is the vague 'etc.', but the overall structure is exemplary for a simple getter.

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 that there is no output schema and only a brief description, the agent cannot fully predict the shape or breadth of the response beyond 'categories (id/name/slug)'. For a simple, zero-parameter tool this may be adequate, but 'etc.' leaves room for ambiguity about what other configuration fields exist (e.g., site name, logo, settings). The absence of explicit return-value documentation lowers completeness.

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 schema provides no meaningful constraints. Per rubric, the baseline is 4. The description adds helpful information about the return payload (categories with id/name/slug), which further compensates for the lack of parameters.

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 ('Get') and resource ('site configuration'), with concrete examples of the returned data ('categories (id/name/slug)'). It clearly distinguishes this tool from sibling tools by indicating it returns global site configuration rather than user or topic-specific data.

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 you need site configuration or category metadata. However, there is no explicit guidance about when not to use it or which alternative tools might be better suited for related but distinct purposes (e.g., list_category_topics for category-specific content). The mention of 'Anonymous' provides some usage context but no exclusion criteria.

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