taiga_timeline_profile

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose an important trait: only public events are returned, which is a meaningful scope limitation. However, it omits other behavioral aspects like pagination behavior, authentication requirements, or return format, so transparency is partial.

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 one short sentence that immediately conveys the action and scope. There is no filler or redundant information. It is appropriately sized for a simple read operation.

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 two-parameter read tool, the description provides enough to start, but it misses some context that would help in practice: it does not mention pagination defaults or how results are structured (no output schema exists). The ambiguity with taiga_timeline_user is also a gap in contextual completeness, as the agent may not know which timeline tool fits the user's request.

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 provides a description for 'user_id' (50% coverage) but leaves 'page' undocumented. The tool description adds no parameter semantics beyond what the schema provides, failing to compensate for the undocumented 'page' parameter. An agent might not know how to use pagination without further hints.

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 a verb and resource: 'Get timeline for a user profile'. It also specifies a scope ('public events only'), which helps set expectations. However, it does not distinguish this tool from the sibling 'taiga_timeline_user', which could easily be the same purpose, so it lacks full differentiation.

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 phrase 'public events only' gives some context about the content delivered, but it does not provide guidance on when to choose this tool over alternatives like taiga_timeline_user or taiga_timeline_project. There is no explicit mention of conditions, exclusions, or alternative tool recommendations, leaving the agent to guess.

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