search

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function without mentioning any behavioral traits such as read-only nature, rate limits, authentication requirements, or side effects. The description adds minimal transparency beyond the obvious.

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 very concise with a single sentence that efficiently conveys the tool's purpose. It is appropriately sized and front-loaded, though it could benefit from slightly more structure to separate the general function from parameter hints.

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 complexity (4 parameters, multiple search types), no output schema, and many siblings, the description is incomplete. It does not explain the return format, default behavior when no search_type is specified, or how results are aggregated across categories. This leaves significant gaps for an agent to correctly invoke and interpret the tool.

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 input schema has 100% parameter description coverage, so the schema already documents each parameter's purpose. The description does not add any additional meaning beyond listing the searchable categories, thus providing no extra value for 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 clearly states the tool searches Mastodon for accounts, statuses, and hashtags, specifying the verb and resource. However, it does not differentiate from sibling tools like account_search or timeline_hashtag, which have more specific 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 no guidance on when to use this tool versus alternatives. It lacks any context about when it is appropriate to use search compared to account_search or timeline tools, leaving the agent without usage decision support.

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