Get the current engagement

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses that Markdown output is automatically trimmed for large engagements, states that format='json' returns the complete raw JSON, and explains how compact and limit override/control trimming. This is meaningful non-obvious behavior beyond the schema.

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 front-loaded with the core action and then details formatting behavior. It is relatively dense and bilingual, but the extra length is justified by the tool's non-trivial output behavior and the bilingual audience.

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 low-complexity retrieval tool with no required parameters and no output schema, the description covers the main behavioral context: output format, trimming behavior, and row-count controls. It does not explain what 'the engagement' contains or error cases, but the essentials for calling and interpreting results are present.

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%, so the baseline is 3, but the description adds value by explaining behavior tied to parameters: format='json' yields complete raw JSON, compact=false shows every row, and limit changes the row count. This goes beyond the schema's per-parameter descriptions.

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 clear verb and resource: '保存されているエンゲージメントの内容を返す' / 'Return the stored engagement'. It is distinguishable from list_engagements and other engagement tools by focusing on the current/stored engagement, though it does not explicitly name any sibling alternative.

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 useful within-tool guidance for format, compact, and limit options, but it provides no guidance on when to choose this tool versus siblings like list_engagements, switch_engagement, or check_engagement_health. No alternatives or exclusions are mentioned.

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