senior_brief

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

No annotations are provided, so the description carries full burden. The description states what the tool returns but does not disclose behavioral traits such as whether it modifies state (likely read-only), authentication requirements, rate limits, or whether it aggregates from multiple stores. This lack of behavioral context is a significant gap.

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. It is efficient but lacks structure; no separate sections for when to use or parameter details. Given the missing information, it could benefit from more structure, but it stays on point.

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 has 5 parameters, no output schema, and no annotations. The description only covers the output content but omits crucial context: parameter meanings, return format, side effects, and how it differs from sibling tools. For such a complex tool, the description is severely incomplete.

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 0%, and the description does not explain any of the five parameters (topic, repo_id, memory_limit, top_k, chunk_top_k). Parameter names hint at their purpose but are not officially documented. The description adds no semantic value beyond the schema's type and default values.

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 a 'senior-developer brief' for a topic, listing specific components (architecture profile, conventions, hazards, workflows, related durable memories). It effectively distinguishes the tool from siblings like 'brain_search' (which searches memories) or 'profile_get' (which gets a profile). However, it could be more precise about the verb.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or relationships to other tools like 'rag_query_data' or 'profile_get'. The agent must infer usage from the purpose.

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